[
https://issues.redhat.com/browse/WFLY-14259?page=com.atlassian.jira.plugi...
]
Dominik Lepczyński commented on WFLY-14259:
-------------------------------------------
I think I've found the issue. WildFly is launched with -Djsse.enableSNIExtension=false
and that's why it fails to connect. After all these years running on WildFly I
don't remember the source of the suggestion to disable SNI. Probably comes from times
before JDK fully supported TLS v.1.3.
Case closed.
URL.openStream fails handshake on WildFly
-----------------------------------------
Key: WFLY-14259
URL:
https://issues.redhat.com/browse/WFLY-14259
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 20.0.0.Final, 20.0.1.Final
Reporter: Dominik Lepczyński
Priority: Major
There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection
works on the same JDK and machine in a standalone Java program. Only when the code is
executed on WildFly the server_name extension is going AWOL from ClientHello message, and
the connection fails with handshake_failure. It seems to be a bug in WildFly, because it
happens only when running on WildFly with the rest of the code identical.
Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)