fix: username onboarding on third party login/link #1966
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If there is an existing user with a username and that user decides to link a third party account and username onboarding on login is enabled then logging in via third party results in a username onboarding prompt but if the user enters a username, then this leads to an error: if it is the same username it results in a "username already taken" error, if it is a different username it results in a technical error (unique constraint violation on the DB level because there already is a username for this user). The username prompt should not appear if the username is already set.
Implementation
There's already a check in place for ensuring that a username is set but the persister used to retrieve the identity does not preload the username, hence the check fails.
How to test
Do a before/after of: