8312383: Log X509ExtendedKeyManager implementation class name in TLS/SSL connection

[pkumaraswamy]

This is a clean backport.

I have verified the fix and results are attached here
x509_testing.zip

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8312383 needs maintainer approval

Issue

• JDK-8312383: Log X509ExtendedKeyManager implementation class name in TLS/SSL connection (Enhancement - P4 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 103

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk22u/pull/103.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back pkumaraswamy! 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]

@pkumaraswamy 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:

8312383: Log X509ExtendedKeyManager implementation class name in TLS/SSL connection

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

➡️ 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 issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (410af505)

[pkumaraswamy]

/integrate

[openjdk]

@pkumaraswamy
Your change (at version 410af50) is now ready to be sponsored by a Committer.

[coffeys]

/sponsor

[openjdk]

Going to push as commit 2ec72f9.

[openjdk]

@coffeys @pkumaraswamy Pushed as commit 2ec72f9.

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