Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-dev] trying to get jetty properties honored in private SSL module

I'm using jetty 9.3.21.v20170918, and I'm running into inconsistent
behavior about processing jetty properties.

The inconsistency is that this setting seemes to be only honored
from the start.ini file, but not from within a module file.

I'd appreciate a second set of eyes, if someone is willing to review. I must
be missing something basic here. :/

I'm specifically trying to set


Here, I do all my testing from

Create my own module based on the stock 'ssl' module; alter it to
set the property's value; basically, replace the commented-out
property with the value I want:

  cp -p ../modules/ssl.mod modules/my-ssl.mod
  perl -pi -e 's/^ssl$/my-ssl/' modules/my-ssl.mod
  perl -pi -e 's/^(# )*(jetty.sslContext.wantClientAuth)=.*/${2}=true/' \
  grep wantClientAuth modules/my-ssl.mod

    (shows jetty.sslContext.wantClientAuth=true in [ini-template])

Observe that this property doesn't show up in '--list-config':

  java -jar ../start.jar --module=my-ssl --list-config | grep wantClientAuth

If I add it to start.ini, it now shows up:

  echo jetty.sslContext.wantClientAuth=true >> start.ini
  java -jar ../start.jar --module=my-ssl --list-config | grep wantClientAuth

   (shows jetty.sslContext.wantClientAuth = true)

Should --list-config show my setting in my module?

I'm testing the effect using OpenSSL.  When working, that looks
like this:

  openssl s_client -connect localhost:8443 \
    -state -debug -cert example.pem -key example.pem < /dev/null 2>&1 |
  grep 'write client certificate'

And the result looks like this:

  0220 - d1 64 40 4a 27 10 e4 28-0d 5d a7 cSSL_connect:SSLv3 write client certificate A

So, irrespective of what '--list-config' presents, I can test to
see if the property is indeed being utilized my the module.

Brian Reichert				<reichert@xxxxxxxxxxx>
BSD admin/developer at large	

Back to the top