JDK-8056026 : Debug security logging should print Provider used for each crypto operation
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: javax.crypto
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2014-08-26
  • Updated: 2016-12-08
  • Resolved: 2014-09-25
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.
7u80Fixed 8u40Fixed 9 b33Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Working an issue at moment where we're unable to pinpoint what Provider is being used in the JDK toolkit of providers during SSL sessions. In a solaris T5 environment, you ideally want to load all crypto operations on to the UCrypto provider. That's not always easy to detect from the verbose logging that's currently available.

Users may have environments where they expect hardware crypto acceleration to be in use (Ucrypto, SunPKCS11) but there's no easy way to tell from verbose JDK security logging output.
I would imagine this extra tracing would get printed when the java.security.debug=provider debug setting is enabled where as JDK-7013776 concentrates on the javax.net.debug system property. side note : (another project might be migrating the SSL verbose logging into the java.security.debug flag) - providing one security debug flag which can accept multiple arguments/values may help create a central support option/flag for users of security APIs in the JDK.

This should probably be added to the other debug output bug. JDK-7013776