-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor doc fixes for PKI realm #103831
Minor doc fixes for PKI realm #103831
Conversation
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-security (Team:Security) |
@@ -1015,8 +1015,9 @@ the following settings: | |||
`username_pattern`:: | |||
(<<static-cluster-setting,Static>>) | |||
The regular expression pattern used to extract the username from the | |||
certificate DN. The first match group is the used as the username. | |||
Defaults to `CN=(.*?)(?:,\|$)`. | |||
certificate DN. The username is used for auditing and logging (not role mapping). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The not role mapping
isn't strictly true (and I expect some readers to be confused).
If you use the role mapping API, then you can map on username.
It's also use for delegated authorization (lookup realms) which is the scenario that (I think) prompted this clarification.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Tim ! I missed those usages. I have updated the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 Backport successful
|
Remove the reference to the transport client and clarify the usage of username_pattern
Remove the reference to the transport client and clarify the usage of
username_pattern