SocialBehavior: Set provider in extractAccountData before marshalling #1152
+1
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For save the new SocialAccount need to set the provider field (Validation error)
Member
|
I've included this change into #1164 preparing a new version 16 with other changes too. Let me know if you need it also in 15 and we'll apply it there too. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Ensure the provider field is included in extractAccountData so associated SocialAccounts validation passes during newEntity marshalling.
Fixes missing 'provider' validation error observed with Keycloak (and potentially others) when creating users.
No impact on existing accounts; provider remains enforced later as well.
Aligns data flow with validator requirements to avoid premature validation failures.