8325766: Extend CertificateBuilder to create trust and end entity certificates programmatically

[deepakdamodaran]

25u backport of 31847149c1956b23c19a99309982660b4bbdd2d6
Almost clean except one extra import statement at line no 44.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8325766 needs maintainer approval

Issue

• JDK-8325766: Extend CertificateBuilder to create trust and end entity certificates programmatically (Enhancement - P4 - Approved)

Reviewers

• Sean Coffey (@coffeys - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk25u.git pull/263/head:pull/263
$ git checkout pull/263

Update a local copy of the PR:
$ git checkout pull/263
$ git pull https://git.openjdk.org/jdk25u.git pull/263/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 263

View PR using the GUI difftool:
$ git pr show -t 263

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk25u/pull/263.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back ddamodaran! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@deepakdamodaran This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8325766: Extend CertificateBuilder to create trust and end entity certificates programmatically

Reviewed-by: coffeys

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 1 new commit pushed to the master branch:

• 7c60413: 8368367: Test jdk/jfr/event/gc/detailed/TestGCHeapMemoryUsageEvent.java fails jdk.GCHeapMemoryUsage "expected 0 > 0"

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@coffeys) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

This backport pull request has now been updated with the original issue, but not the original commit. If you have the original commit hash, please update the pull request title with Backport <hash>.

[mlbridge]

Webrevs

• 00: Full (a86d489a)

[deepakdamodaran]

/approval JDK-8325766 request. Need to fix to achieve parity, Test change only, No risk.

[openjdk]

@deepakdamodaran
JDK-8325766: The approval request has been created successfully.

[coffeys]

LGTM

[deepakdamodaran]

/integrate

[openjdk]

@deepakdamodaran
Your change (at version a86d489) is now ready to be sponsored by a Committer.

[coffeys]

/sponsor

[openjdk]

Going to push as commit 61a014e.
Since your change was applied there has been 1 commit pushed to the master branch:

• 7c60413: 8368367: Test jdk/jfr/event/gc/detailed/TestGCHeapMemoryUsageEvent.java fails jdk.GCHeapMemoryUsage "expected 0 > 0"

Your commit was automatically rebased without conflicts.

[openjdk]

@coffeys @deepakdamodaran Pushed as commit 61a014e.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.