Add support for RDN attribute name matching to PKI realm. #137931
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds configuration options to the PKI Realm for principal extraction from the client certificate based on a relative distinguished name (RDN) attribute value.
The following Elasticsearch YAML configuration options is included:
username_rdn_name- the RDN attribute name to use, e.g.CNThe implementation is based on text parsing of the RFC 2253 formatted text of the X500 distinguished name using the UnboundID LDAP SDK library.
Caveat: this approach only supports standard LDAP attribute types, such as
CN,O,OU,UID, etc.Non-LDAP extensions, such as
EMAILADDRESS, and custom OIDs are not supported.Examples:
CN=John Doe, OU=Security Team, OU=Engineering, O=ElasticCNJohn DoeUID=abc123, OU=Security Team, OU=Engineering, O=ElasticUIDabc123UID=abc123, OU=Security Team, OU=Engineering, O=ElasticCN