Pass user info to auth0_before_login action #817
Merged
Conversation
This file contains 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
evansims
approved these changes
Feb 11, 2021
|
Hey, @nicecatch! 👋 This looks like a good addition to me; thanks for your contribution! Appreciate it 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There are situations in which we want to check whether the user is authorized to access a wordpress website based on the info passed by Auth0 (contained in app_metadata or user_metadata)
This PR aim is for this info to be available in the auth0_before_login action
Why not use auth0_user_login?
Because at that point the user is already logged in.
Letting the user login and then rejecting him is not ideal, especially if we want to show a custom error page