JDK-8227707 : https connection over TLSv1.2 fails
  • Type: Bug
  • Component: security-libs
  • Sub-Component: javax.net.ssl
  • Affected Version: 11,12,13
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2019-07-16
  • Updated: 2020-06-23
  • Resolved: 2019-08-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 14
14Resolved
Related Reports
Duplicate :  
JDK-8229720 - New JSSE APIs to configure named groups and signature algorithms
Relates :  
JDK-8242141 - New System Properties to configure the TLS signature schemes
Description
JDK 13 has TLS compatibility issue with Google server TLS implementation.

Problematic Protocol: TLSv1.2
Host: www.google.com
Host detail: 2 key types: ���EC 256 bits��� and ���RSA 2048 bits���
                   Problematic CipherSuit: TLS_*_RSA_*

While it works expected for < TLSv1.2 and TLSv1.3.
Comments
Workaround for this issue - Use the new system property "jdk.tls.client.SignatureSchemes" defined in task JDK-8242141 . Eg: jdk/bin/java -Djdk.tls.client.SignatureSchemes="rsa_pss_rsae_sha256, rsa_pss_rsae_sha384, rsa_pss_rsae_sha512, rsa_pss_pss_sha256, rsa_pss_pss_sha384, rsa_pss_pss_sha512, rsa_pkcs1_sha256, rsa_pkcs1_sha384, rsa_pkcs1_sha512, dsa_sha256, ecdsa_sha224, rsa_sha224, dsa_sha224, ecdsa_sha1, rsa_pkcs1_sha1, dsa_sha1" TestHttpsClient
08-05-2020
Same issue is there with host www.youtube.com
03-12-2019
JDK-8229720 will be used to add the system property to customize signature algorithms.
16-08-2019
[~rhalade] I agreed. It looks more like a google.com issue. We may want a solution to workaround the issue if customers run into the problem. I was wondering to add a new system property to customize the signature algorithms.
16-07-2019
This sounds like not a jdk issue but an external to google.com. We also tested few other sites with TLSv1.3 support and they are working fine with 1.2.
16-07-2019
Per my test, JDK is able to connect OpenSSL impl. And if disable the signature_algorithms but have signature_algorithms_cert extension, JDK is able to connection to google.com. OpenSSL could connect to google.com with the signature_algorithms extension, with less options. Maybe, google.com is not able to identify some signature algorithms in the extension in its TLS 1.2 implementation.
16-07-2019
This issue may be caused by JSSE TLSv1.3 implementation (JDK-8196584). The attached test passes with jdk11+19. JDK-8196584 was integrated to jdk11+20.
16-07-2019
It looks google.com complains JSSE ClientHello over TLSv1.2. The server raises fatal handshak_failure immediately after receive the client hello.
16-07-2019
thanks! lowering the priority to P3 after ILW.
16-07-2019
The attached TestHttpsClient.java also fails with JDK 11 (11.0.4+9-LTS) and JDK 12 (12.0.2+8). But it passes with JDK 8 (1.8.0_221-b78).
16-07-2019