Skip to content
Merged
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/user-guide/authenticating-with-client-certificates.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,17 @@ If using the internal API ML mapper (default from Zowe v3) and the MAP / CERTMAP

:::tip
To disable the API ML mapper, ensure that you set the parameter `components.gateway.apiml.security.useInternalMapper` to `false`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pablocarle Hi Pablo, could you please confirm whether the text is correct? Kindly let us know if any further changes to the text are required. Thanks for your help!
CC: @gauravs-20 @ArooshLele @1000TurquoisePogs @anaxceron @janan07

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.
:::

:::note
API ML currently only supports `DIGTNMAP` for certificate-to-user mapping.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

:::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The statement is updated.



</details>

**ACF2**
Expand Down
Loading