Lost attributes with surrogate main #6019
Closed
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.
When the surrogate feature is enabled, the SurrogatePrincipalElectionStrategy is used instead of DefaultPrincipalElectionStrategy.
SPES selects attributes that are 'attached' to the principal, in comparison to DPES, which selects the merged collection of attributes from all principals.
When authentication flow involves more than one authentication method, with resulting multiple principals each having different attribute sets, SPES will select an attribute set from only one of the principals.
e.g., ldap authn with ldap attributes, duo MFA with duo attributes; only the duo attributes are included in the nominated principal.
This change adds a surrogate specific principal which is checked by SPES when selecting attributes. Only if the principal is a surrogate will the surrogate's attributes be returned. Otherwise behaviour is as in DPES.