Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Failing assertion does not necessarily imply UNAUTHORIZED_CLIENT #79

Open
danielevans opened this issue Jan 20, 2015 · 0 comments
Open

Failing assertion does not necessarily imply UNAUTHORIZED_CLIENT #79

danielevans opened this issue Jan 20, 2015 · 0 comments

Comments

@danielevans
Copy link

When an assertion fails (for instance if a Facebook token were incorrect or the user had post-authorization deleted the application) the following code will automatically mark the request as an UNAUTHORIZED_CLIENT when INVALID_GRANT would be more accurate.
https://github.com/songkick/oauth2-provider/blob/master/lib/songkick/oauth2/provider/exchange.rb#L191-L194
@danielevans danielevans changed the title Failing assertion does not necessarily imply Failing assertion does not necessarily imply UNAUTHORIZED_CLIENT Jan 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danielevans