Updated authenticating-with-client-certificates.md

[ArooshLele]

List the file(s) included in this PR: authenticating-with-client-certificates.md

Describe your pull request here:
A note is added.
The proposed note may be specific for a customer, based on the feedback from that customer. At this stage, it is unknown whether the note is fully factually correct and valid for all customers. If the note needs to include more information, please add SMEs to this Pull Request. They could provide a feedback.
Thank you,
CC: @ArooshLele @gauravs-20

After creating the PR, follow the instructions in the comments.

[github-actions]

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

• Add the label review: doc.
• Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
• Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
  • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
• Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
• Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

[github-actions]

🚀 Deployed on https://69929f50417610291af2ba58--zowe-docs-master.netlify.app

[pablocarle]

This is only if disabling the internal mapper, but with internal mapper enabled it supports both mapping and adding the certificate to the user:

https://github.com/zowe/docs-site/pull/4868/changes#diff-aeab6f0cab716353a01b0056f8553738d3b9f5a4242f82bdc67b2641f03acd22R115

[ArooshLele]

@pablocarle Thanks for your feedback.

The following is a draft of the reworded note.
Please let me know whether it is correct or whether any information is to be added.
Thanks in advance!

Note:
If the internal mapper is disabled, then API ML only supports DIGTNMAP for certificate-to-user mapping.
If the internal mapper is enabled, then API ML supports the following:

• DIGTNMAP for certificate-to-user mapping.
• Adding the certificate to the user.
  CC: @ArooshLele @hrishikesh-nalawade @1000TurquoisePogs @gauravs-20 @janan07

[ArooshLele]

Hello Pablo @pablocarle,
Please review the lines from line 74 to line 77.
The text to be reviewed is:
Note:
If the internal mapper is disabled, then API ML only supports DIGTNMAP for certificate-to-user mapping.
If the internal mapper is enabled, then API ML supports the following:

• DIGTNMAP for certificate-to-user mapping.
• Adding the certificate to the user.

CC: @gauravs-20 @ArooshLele @1000TurquoisePogs @hrishikesh-nalawade

[pablocarle]

This is backwards, the default in v3 is internal mapper:

Internal mapper: supports DIGTNMAP and adding the cert to the user.
ZSS mapper: only supports adding the certificate to the user.

The note says that API ML only supports DIGTNMAP, but this is not true. In the default internal mapper, both are supported.

[ArooshLele]

The statement is updated.

[pablocarle]

is this correct in upper case?

[ArooshLele]

is this correct in upper case?

The text is edited. It is now in the lower case.

[pablocarle]

I think this statement should be removed, as it could be confusing, the guide is already written to recommend not changing the default

[ArooshLele]

I think this statement should be removed, as it could be confusing, the guide is already written to recommend not changing the default

Noted. The statement [To disable the API ML mapper, ensure that you set the parameter components.gateway.apiml.security.useInternalMapper to false.] is removed.