Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression: Client certificates do not work in 9.4.15.v20190215+ #3554

Closed
byteit101 opened this issue Apr 15, 2019 · 4 comments
Closed

Regression: Client certificates do not work in 9.4.15.v20190215+ #3554

byteit101 opened this issue Apr 15, 2019 · 4 comments

Comments

@byteit101
Copy link

Using a client certificate set up, I get java.security.cert.CertificateException: No subject alternative names present and a terminated TLS handshake Description: Certificate Unknown (46) with jetty 9.4.15.v20190215 and 9.4.16.v20190411. Same client passes on 9.3.x and 9.4.9 - 9.4.14. (I didn't test pre 9.4.9)

I used the downloaded demo.jar by following https://www.eclipse.org/jetty/documentation/current/jetty-ssl-distribution.html#client-certificate-authentication with certificates generated from https://gist.github.com/jankronquist/6412839 and jetty.sslContext.needClientAuth=true

When I download 9.4.14 or earlier, following the documentation allows my client to connect successfully, whereas 9.4.15 and later give the aforementioned error.

@joakime
Copy link
Contributor

joakime commented Apr 15, 2019

Sounds like you hit #3454 and the associated bug detected after changes in #3480 was released.

@joakime
Copy link
Contributor

joakime commented Apr 15, 2019

Your SNI issue could also be related to #2896 or #2886

@joakime
Copy link
Contributor

joakime commented Apr 15, 2019

We've had reports that using endpointIdentificationAlgorithm=null works for people that are only using server side SSL (does not apply for jetty-client use for SSL on same server)

@sbordet
Copy link
Contributor

sbordet commented Apr 16, 2019

@byteit101 please see this comment.

Set endpointIdentificationAlgorithm=null or better yet use SslContextFactory.Server instead of a plain SslContextFactory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants