Notify client of OAuth2Errors + fix all lint and PEP8 errors #138
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
* Properly report non-fatal client errors to the client (like e.g. invalid_scope) according to http://tools.ietf.org/html/rfc6749#section-4.1.2.1
This was referenced Aug 27, 2014
|
Thanks. Merged in 3f766bb |
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.
invalid_scope) according to http://tools.ietf.org/html/rfc6749#section-4.1.2.1
The unknown exception handling introduced in 0.7.0 catches all oauthlib's OAuth2Errors as well, which makes it impossible to properly handle e.g. invalid scopes. All fatal client errors will properly be reported to the resource owner, while non-fatal client errors (like invalid scope) will be reported to the client.