-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
ClientCertAuthenticator is not taking account SslContext configuration #5933
Comments
@lachlan-roberts do you want to tackle this? Ideally, web applications that need this kind of authentication will need to setup a custom Jetty context XML file, where the configure the authenticator. However, we want to have a good default if that custom XML is not there. The idea is that, in If there is more than 1 |
…om server Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
…om server Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
Added SslClientCertAuthenticator Co-authored-by: olivier lamy <oliver.lamy@gmail.com> Signed-off-by: Greg Wilkins <gregw@webtide.com>
Jetty version
10.0.x (but might a 9.4.x issue as well)
Description
Using CLIENT-CERT as login with a configured trustStore via ssl.ini.
The used
ClientCertAuthenticator
instance is not using the configuration from the instance SslContextFactory instance.The text was updated successfully, but these errors were encountered: