Ability to define required scopes by the middleware #2
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
…n error to be thrown when a required scope is not authorized
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR brings the ability to add an array with required scopes (permissions) which are checked against the authorized scopes from the user. Facebook allows users the choice to dis-allow scopes our application really needs. Say, for example, we really need the email scope for our application to work, but the user doesn't want to authorize us being able to view their email address. This allows us to throw an error back to the client saying we do really need that email scope.
The client can then keep asking for the right scopes until the users either choses to authorize it, or decides not to use facebook for our application.