Refresh identity traits on social / SSO login

[aeneasr]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Network project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe your problem

Currently, social sign in only executes the JsonNet during registration. However, multiple questions have come up in several issues how this can be solved for linking sign ins, or when the user sign ins again - to keep the data fresh.

Example of such a discussion: ory/network#164 (comment) (there are more!)

Describe your ideal solution

The jsonnet should be executed on sign in and on linking social sign in as well. It will have to respect the existing user data as well (so it needs to be available in the context).

Workarounds or alternatives

There are no workarounds for this.

Version

master

Additional Context

No response

[netthier]

Already posted this in one of the other issues, but I'm wondering what would happen to the user data if the Jsonnet code and schema are changed between logins.
Would the user be effectively recreated with the most recent schema and Jsonnet, or would some old version be run?

[aeneasr]

We would add the current identity data to the jsonnet context, and then it's your decision

[netthier]

Has there been any progress on this?

[kmherrmann]

We've added the ability to update identities from webhooks, see here: https://www.ory.sh/docs/guides/integrate-with-ory-cloud-through-webhooks#update-identity-traits

Would that solve the problem for you?

[netthier]

We've added the ability to update identities from webhooks, see here: https://www.ory.sh/docs/guides/integrate-with-ory-cloud-through-webhooks#update-identity-traits

Would that solve the problem for you?

No, as I need the update to happen during sign-in and the docs state the following:

Modifying the identity is currently only possible during the registration and settings flows.

In my case an external social login is the source of truth for identity data. I want the Jsonnet logic that constructs the identity from the JWT to run on every sign-in, potentially updating out-of-sync values.

[kmherrmann]

I see, makes sense, thanks. I'll add it to the backlog, but a PR would accelerate it :)