JDK-8075902 : Update security provider docs for changes under 8038084 and 7191662
  • Type: Task
  • Component: docs
  • Sub-Component: guides
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-03-25
  • Updated: 2017-09-07
  • Resolved: 2017-09-07
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 9
9Fixed
Related Reports
Relates :  
JDK-7191662 - JCE providers should be located via ServiceLoader
Relates :  
JDK-8038084 - CertStore needs a way to add new CertStore types
Description
Security documentations need to be updated for the following:
1) the addition of new provider "JdkLDAP" for LDAP CertStore implementation (which was in SUN provider)
2) the addition of new provider "JdkSASL" for GSSAPI SaslClientFactory/SaslServerFactory implementations (which was in SunSASL provider)
3) the provider preference list inside java.security uses provider name by default instead of the full class name.
4) the new Provider.configure(String... configArgs) API which can be used to create custom PKCS11 providers at runtime.
Comments
Also, the following example in section 2.2 of the PKCS11 Reference Guide: String configName = "/opt/bar/cfg/pkcs11.cfg"; Provider p = new sun.security.pkcs11.SunPKCS11(configName); Security.addProvider(p); should be replaced with: String configName = "/opt/bar/cfg/pkcs11.cfg"; Provider p = Security.getProvider("SunPKCS11"); p.configure(configName); Security.addProvider(p); and the java.security provider list will need to be updated in section 2.5.1
25-02-2016
I've bumped this to a P2 as it is important that the security guides are updated in JDK 9 to reflect the changes to the security provider configuration.
20-06-2015