Complete rfc7009- OAuth 2.0 Token Revocation #398
Draft
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
fix(refresh-token): validate scope before revoking token #390
Draft: OAuth 2.0 Token Revocation / rfc7009
Member
Author
|
Will continue, once this is merged: node-oauth/formats#3 |
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.
Summary
This is a continuation of #379 to implement RFC7009 token revocation.
Linked issue(s)
#343
Involved parts of the project
OAuth2Server, Handlers, Grants, Tests, Docs
Added tests?
Expecting to add tests for full compliance
OAuth2 standard
RFC 7009 - https://www.rfc-editor.org/rfc/rfc7009
Reproduction
TBD