Details
-
Bug
-
Resolution: Fixed
-
P2
-
8u261
-
b01
-
Verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8254147 | 8u271 | Dmitry Markov | P2 | Resolved | Fixed | b31 |
JDK-8253400 | 8u261 | Dmitry Markov | P2 | Closed | Fixed | b36 |
JDK-8257267 | emb-8u281 | Dmitry Markov | P2 | Resolved | Fixed | team |
Description
Update to 8u261 causes TLS handshake failure.
In test configuration there are several handshake requests and only the first one is successful. The subsequent ones have an issue with client Certificate and provide the server with the empty cert list. As a result the server rejects client certificate handshake message.
In test configuration there are several handshake requests and only the first one is successful. The subsequent ones have an issue with client Certificate and provide the server with the empty cert list. As a result the server rejects client certificate handshake message.
Attachments
Issue Links
- backported by
-
JDK-8254147 Empty client certificate issue during TLS handshake
-
- Resolved
-
-
JDK-8257267 Empty client certificate issue during TLS handshake
-
- Resolved
-
-
JDK-8253400 Empty client certificate issue during TLS handshake
-
- Closed
-
- relates to
-
JDK-8206925 Support the certificate_authorities extension
-
- Resolved
-
-
JDK-8262186 Call X509KeyManager.chooseClientAlias once for all key types
-
- Closed
-