I've checked on my testbox (19.02.001+11.0.2 openjdk) but I get a connect with sslpoke (postman on https working aswell).
Do you have more information in the log if you use -Djavax.net.debug=all ?
I just retested the issue and now I do have the same handshake error, however i haven't changed anything on configuration.
Maybe the problem is with config & cipher suite?
On my box, jdk 1.8 client is using Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 while jdk 11.02 client is using "cipher suite" : "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384(0xC030)",
I haven't found a way yet to disable or enforce a certain ciphersuite on command line for crosschecking.
1 of 1 people found this helpful
I managed to disable TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 and then TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is used (same as on java 1.8) however it throws the same exception.
seems like a similar problem however I have no clue how to implement/test this.
Suggest you to open a ticket with BMC for clarification.
Thank you Andreas for your help
I have a case open with BMC support and they have just confirmed also that open jdk is at fault and are looking to a possible fix.
3 of 3 people found this helpful
It was confirmed that it is a OpenJDK 11 bug(not recognizing the SSL certificate for jetty) and will be fixed in v13.