Use existing identity traits when automatically linking credentials about kratos HOT 2 OPEN

For what it's worth, without #3311, it's basically impossible to link OIDC natively, unless you have just an email address in your identity schema (and want to support Sign in with Apple).

from kratos.

Having experimented with it a bit more, I'd also like to add that since this new registration is always done on OIDC login conflict, there is no way to opt out of the behaviour. For example, the internal registration still calls all of the registration hooks. As a consumer of the API, this seems unexpected, and in some cases, completely unwanted. There is no way to prevent these hooks from being called, which is required if hooks expect information only available in a legitimate registration (as above) or if those hooks perform actions which you only want on legitimate registration.

Intuitively, calling registration hooks on a login endpoint doesn't make sense and I think using an internal registration flow was a mistake for automatic account linking.

from kratos.