Open sbordet opened 3 years ago
This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions.
Jetty version 10.0.x
Description During the TLS handshake, in case of
needClientAuth
, the client may send an invalid (e.g. expired) certificate. The validation checks are performed by theTrustManager
and if they fail there is no way to access the expired client certificate, for example inSslHandshakeListener.handshakeFailed()
, as it is not exposed viaSSLSession.getPeerCertificate()
, etc.The only option would be to wrap the
TrustManager
, but that requires subclassingSslContextFactory.Server
and overridinggetTrustManager()
, whose signature is likely to change in light of #6054.Would be great to have a more stable way to provide hooks into the
TrustManager
in a simpler way.