Fix: Conflicting profile properties between profile and attributes #593
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.
Description
passport-saml/src/passport-saml/saml.ts
Line 1319 in f1a436f
It is currently possible to override some default properties of the
profile
object inprocessValidlySignedAssertionAsync
method.This can be done if any property like
Issuer
is also present in the attribute mapping. The expected behavior here should be that the properties (Issuer
,inResponseTo
,sessionIndex
,nameID
,nameIDFormat
,nameQualifier
,spNameQualifier
) will probably already be present in the profile, and in that case they shouldn't be overridden by the same named attribute in attribute mapping.This issue can be handled gracefully by simply skipping the value from attribute mapping or an error can be thrown. This PR handles the issue gracefully.
Checklist: