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

oauth2: Revoking access or refresh tokens should revoke past and future tokens too #278

Closed
aeneasr opened this issue May 25, 2018 · 0 comments
Labels
breaking change Changes behavior in a breaking manner. bug Something is not working.

Comments

@aeneasr
Copy link
Member

aeneasr commented May 25, 2018

No description provided.

@aeneasr aeneasr added bug Something is not working. breaking change Changes behavior in a breaking manner. labels May 25, 2018
aeneasr pushed a commit that referenced this issue May 28, 2018
This patch resolves several issues related to token revokation as well as duplicate authorize code usage:

* oauth2: Revoking access or refresh tokens should revoke past and future tokens too
* oauth2: Revoke access and refresh tokens when authorize code is used twice

Additionally, this patch resolves an issue where refreshing a token would not revoke previous tokens.

Closes #278
Closes #280
budougumi0617 added a commit to budougumi0617/fosite that referenced this issue May 10, 2019
This patch resolves several issues related to token revokation as well as duplicate authorize code usage:

* oauth2: Revoking access or refresh tokens should revoke past and future tokens too
* oauth2: Revoke access and refresh tokens when authorize code is used twice

Additionally, this patch resolves an issue where refreshing a token would not revoke previous tokens.

Closes ory#278
Closes ory#280
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Changes behavior in a breaking manner. bug Something is not working.
Projects
None yet
Development

No branches or pull requests

1 participant