Skip to content
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

Adjust passport script to parameterize whether updates should be applied to user profile or not #987

Closed
jgomer2001 opened this issue Jan 23, 2019 · 1 comment

Comments

@jgomer2001
Copy link
Contributor

commented Jan 23, 2019

In passport flow, the info released by external provider is parsed and an update is applied to local profile in LDAP. That is, the provider is treated as a trusted source of data. If one attribute changes or disappears, the same will reflect locally

There is a special case where no profile edition should take place: Linking of external accounts via casa's account linking plugin.

Info for QA team:

  • An application protected using passport_social or passport_saml should behave as normally (ie if profile data changes at external IDP, the same will happen locally upon the subsequent login)

  • When using Casa configured with account linking plugin + external providers integration, no profile update should take place.

@jgomer2001 jgomer2001 added this to the 3.1.6 milestone Jan 23, 2019

@jgomer2001 jgomer2001 self-assigned this Jan 23, 2019

@jgomer2001

This comment has been minimized.

Copy link
Contributor Author

commented Jan 25, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.