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.

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

Non-Compliant Responses from RFC 7009 Token Revocation #119

Closed
night opened this Issue Mar 26, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@night
Copy link

night commented Mar 26, 2019

Per the RFC, invalid tokens should return a 200, but invalid_request is raised, which makes it a 400 response status.

https://github.com/lepture/authlib/blob/master/authlib/oauth2/rfc7009/revocation.py#L41

The authorization server responds with HTTP status code 200 if the
token has been revoked successfully or if the client submitted an
invalid token.

Note: invalid tokens do not cause an error response since the client
cannot handle such an error in a reasonable way. Moreover, the
purpose of the revocation request, invalidating the particular token,
is already achieved.

More details at https://tools.ietf.org/html/rfc7009#section-2.2

@lepture lepture closed this in 90aff45 Mar 28, 2019

@lepture

This comment has been minimized.

Copy link
Owner

lepture commented Mar 28, 2019

Thanks. I've fixed in 90aff45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.