JDK-8143368 : Document JarSigner and X509CertificateBuilder
  • Type: Enhancement
  • Component: docs
  • Sub-Component: guides
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-11-20
  • Updated: 2019-04-16
  • Resolved: 2019-04-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 11 JDK 13
11Fixed 13Fixed
Related Reports
Blocks :  
JDK-8056174 - New APIs for jar signing
Blocks :  
JDK-8058778 - New APIs for creating certificates and certificate requests
Description
JDK-8056174 introduces the JarSigner API, and JDK-8058778 introduces the X509CertificateBuilder API. They cover functions of jarsigner and keytool which were not possible through public APIs.

I am thinking of two places in the Oracle JDK documentation:

1. JDK-specific APIs. We have a tradition to include security-related com.sun.* APIs in the doc (For example: http://docs.oracle.com/javase/8/docs/jre/api/security/jaas/spec/com/sun/security/auth/package-summary.html). These new APIs should be treated the same.

2. New entries in the security guide at http://docs.oracle.com/javase/8/docs/technotes/guides/security/index.html.

3. New entries to tutorials. Optional.