Open thecodeassassin opened 2 years ago
Thank you for the report! It is true that the JsonNet mapper is not applied on linking credentials. We will need to add a feature to support this use case and also provide means of merging the existing data with the new data!
@aeneasr I hope all is well. Is there any chance this will be picked up soon? It's rather inconvenient for our users seeing as we rely on metadata to assign our users custom roles in Discord.
@kmherrmann @piotrmsc please take a look regarding priorization.
@thecodeassassin are you already on production?
Thank you very much.
Yes, our solution is already in production.
@aeneasr is there a workaround? Can we somehow retrieve their OIDC login id? I need their Discord ID for example. This is our mapping file:
is the claims.sub stored somewhere that we can retrieve so I can build a workaround ?
As far as I can read this, the ID, access, and refresh tokens should be available after linking a provider in the settings flow.
Can you check if this works? https://www.ory.sh/docs/kratos/social-signin/get-tokens
Preflight checklist
Describe the bug
When users sign up with a social the metadata gets applied properly. When they link it later the metadata does not get updated properly.
So it happens on register but not on update settings. I think it's because this PR
https://github.com/ory/kratos/pull/2569
Did not address updating social logins from settings.
Reproducing the bug
Relevant log output
No response
Relevant configuration
No response
Version
Ory Cloud
On which operating system are you observing this issue?
Ory Network
In which environment are you deploying?
Ory Network
Additional Context
No response