|[jetty-users] Jetty SNI - Where's ExtendedSslContextFactory?|
I posted a few days ago about some weird behavior regarding SNI in the latest stable version of Jetty. Seems that Jetty is only responding to HTTPS requests with the *first* certificate in my keystore, even though I have more than one valid certificate there.
In testing Bug 430951, I got everything to work *including* SNI.
So now I'm looking at this:
"I have committed the org/eclipse/jetty/util/ssl/ExtendedSslContextFactory.java
If the KeyStore contains multiple X509 certificates, then the CN element
of the distinguished name is used to select the certificate alias to use for
a connection. Simple wildcard names (eg *.domain.com) are supported."
But when I try this:
<Configure id="sslContextFactory" class="org.eclipse.jetty.util.ssl.ExtendedSslContextFactory">
I get a NoClassDefFoundError, and indeed, if I check jetty-ssl.jar, that class *is* missing.
SNI doesn't work at all if I use org.eclipse.jetty.util.ssl.SslContextFactory.
Help, please? What am I missing? The official documentation even *says* I need to use ExtendedSslContextFactory. http://www.eclipse.org/jetty/documentation/current/configuring-ssl.html#configuring-sslcontextfactory
Back to the top