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] refresh tokens must not be used after user consents revocation #4039

Closed
tcompiegne opened this issue Jun 30, 2020 · 1 comment · Fixed by gravitee-io/gravitee-access-management#862

Comments

@tcompiegne
Copy link
Member

Currently AM do that to check if a refresh token is still valid :

  • the authorization server has revoked the refresh token
  • the refresh token has expired

We should also check if :

  • the user has revoked their consent for authorization
@jhaeyaert
Copy link

After discussion, we agreed that when user revokes an application or a single permission (from Authorized apps screen), we will revoke both all the existing refresh_token and access_token.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants