NameID mapping and Single Logout #47288
Merged
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
Clarify in the documentation that for SAML Single Logout to be functional, the user's principal property should be mapped from a SAML NameID and not a SAML Attribute.
Collaborator
|
Pinging @elastic/es-docs |
Collaborator
|
Pinging @elastic/es-security |
tvernum
reviewed
Oct 4, 2019
| NOTE: You can select to map the SAML `NamedID` value or any other SAML attribute value to the `principal` user | ||
| property. Keep in mind, however, that if a SAML attribute is mapped, the <<saml-logout, Single Logout>> functionality is | ||
| not available. | ||
|
|
Contributor
There was a problem hiding this comment.
Is this true? It shouldn't be.
We need to receive a NameID from the IdP, but I don't think we need to map it to principal.
Contributor
Author
There was a problem hiding this comment.
You're right, I jumped the gun on this without looking at the code closely
tvernum
approved these changes
Oct 4, 2019
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Oct 4, 2019
Clarify in the documentation that for SAML Single Logout to be functional, the Identity Provider needs to release a NameID.
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Oct 4, 2019
Clarify in the documentation that for SAML Single Logout to be functional, the Identity Provider needs to release a NameID.
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Oct 4, 2019
Clarify in the documentation that for SAML Single Logout to be functional, the Identity Provider needs to release a NameID.
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Oct 4, 2019
Clarify in the documentation that for SAML Single Logout to be functional, the Identity Provider needs to release a NameID.
jkakavas
added a commit
that referenced
this pull request
Oct 7, 2019
jkakavas
added a commit
that referenced
this pull request
Oct 7, 2019
jkakavas
added a commit
that referenced
this pull request
Oct 7, 2019
jkakavas
added a commit
that referenced
this pull request
Oct 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Clarify in the documentation that for SAML Single Logout to be
functional, the Identity Provider needs to release a NameID.