-
Notifications
You must be signed in to change notification settings - Fork 475
[BUG] Possibility to overwrite profile fields with data from attributes #543
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
Comments
@gtokarz would you be willing to create a PR with tests for this? |
@cjbarth Yes, I might have some time on Monday to do so |
@gtokarz We are preparing a 3.0 release. Would you be interested in getting this change up for PR in the next few weeks to make it in to 3.x? |
@kriss1897 sure, anything with a |
yes, go ahead with PR |
This attributes are also mounted to profile directly in a non conflicting way.
* Fix: Conflicting profile properties between profile and attributes (#543) * Add assertion attributes to child object on profile (#543) This attributes are also mounted to profile directly in a non conflicting way. Co-authored-by: Shashank Singh Solanki <[email protected]>
Currently attributes are mapped to profile without any check, which might at best cause minor issues with previously present properties from profile object.
To Reproduce
Configure Idp/craft a SAML response with attribute Name set to i.e issuer or other profile field set before attribute mapping. Mapped profile object should now have overwritten issuer field.
Expected behavior
It should check if property already exists on the profile object and only map values when key is not present.
passport-saml/src/passport-saml/saml.ts
Line 1319 in f1a436f
Environment
The text was updated successfully, but these errors were encountered: