JDK-8207174 : Add a new regression test: TrustManagerFactory, KeyManagerFactory and SSLContext can be implemented in different providers
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: javax.net.ssl
  • Affected Version: 8,9,10,11
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2018-07-12
  • Updated: 2024-05-09
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8207029 - Unable to use custom SSLEngine with default TrustManagerFactory after updating to JDK 11 b21
Description
It may be not usual, but the spec allows the TrustManagerFactory, KeyManagerFactory and SSLContext implemented in different providers.  As JDK implements them in the same SunJSSE provider, it is likely to introduce the dependency between them.

Need test cases are needed to use these classes from 2+ different providers, and make sure the provider does not introduce the implementation dependency of them.

See JDK-8207029 for the case used in practice.  Test only bug, the implementation fix has been addressed in JDK-8207029.