Quick question about using social providers: is it...
# general
t
Quick question about using social providers: is it possible to have the data mapped from a social provider always override a defined trait or metadata? say the used has changed their name or username in the social idp. could this be reflected in ory?
m
@thankful-refrigerator-23652 At the moment OIDC claims only get mapped during registration, so its not directly possible to update the traits through an OIDC login. So this would work in this case: 1. user signs up with e.g. nickname as vinckr 2. next time user signs up with OIDC and is prompted to link the accounts. on their OIDC account they have the nickname foobar The behaviour you want here is that foobar would overwrite the vinckr nickname - is that correct? IMHO its not a great user experience - it probably depends on your exact setup/use case. But personally I would be upset if I configure something in GitHub and then things change there because I update something else in my Google account. Is there a specific trait/metadata you have in mind?
t
Thats sad to hear, while i understand that there are some data fields you wouldn't want to touch, there are alot of properties that should be "always" provided from oicd (if one would be allowed). This could be fields like users actual name from external system, users assigned groups in a external identity management system (entra, aws, gc) or even the assigned role to any "company created" oicd resource in said identity management system.
But this might also probably be coming into this from a standing of "identity should have one source of truth", that might not apply in this usecase.
"But personally I would be upset if I configure something in GitHub and then things change there because I update something else in my Google account." i would actually be pretty happy google provided properties would be automatically updated, but if i had multiple providers fight over the same field. possibly the best way would be first come, first serve, in a way
@magnificent-energy-493
BUT. is ths "read-once" strategy only applicable to trais or also Metadata?