JDK-8157707 : Deprecate the java.security.Certificate API with forRemoval=true
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-05-24
  • Updated: 2017-08-02
  • Resolved: 2016-07-01
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
9 b126Fixed
Related Reports
Relates :  
Relates :  
Sub Tasks
JDK-8162610 :  
Description
The java.security.Certificate API has been deprecated since 1.2 and has been superseded by java.security.cert.Certificate and related classes since 1.2. It is no longer necessary to retain this class and it should be removed in a future release.
Comments
FC Extension Request The fix is coded and ready for integration, and the CCC has been approved. The risk level is very low. See the description for justification. The enhancement can be completed within a day of getting approval.
27-06-2016

As part of this change, the internal classes sun.security.x509.CertException and sun.security.x509.CertParseError should be marked for removal (they are already deprecated) and removed when java.security.Certificate is removed. External applications should not be using these internal classes anyway, but it would be good to add forRemoval just to make it very clear they are going away. They both have the following deprecation warning right now: * @deprecated use one of Exceptions defined in the java.security.cert * package. * * @see java.security.Certificate and are not used by any code within the JDK.
15-06-2016