Feat: Custom userProfile for Oauth2 to support login with Keycloak; Include phone to customer when logging in store #155
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.
Currently, Oauth2 is allowing user to login with keycloak, but the generated profile returned by Keycloak doesn't follow the Oauth2 User Profile format so it returns
Your oauth2 account does not contains any email and cannot be used
error.With this change, we can pass an optional option to
oauth2
namedparseProfile
which should return a normalized json profile that follows the Oauth2 User Profile format