简体   繁体   中英

Oauth2/Openid Connect. How to revoke unknown access/refresh tokens

In Oauth or Openid Connect, let's say an attacker takes an access or refresh token and the browser or app's caches are cleaned. Can a user revoke an access or refresh token issued by an Identity Provider if their string is not explicitly known?

If your Token-Provider is at least an OAuth 2.0-Provider, it has to to implement the OAuth 2.0 Token Revocation .
The URL should be delivered by on OpenID Connect-Provider as "revocation_endpoint" in the /.well-known/openid-configuration.

It really depends on the implementation at the Identity Provider but typically you should be able to revoke the at least the refresh token. The refresh token is most often stored in persistent storage at the IDP and a user may login to the IDP to manage client authorizations and refresh tokens. As an example, Google allows users to manage those at: https://security.google.com/settings/security/permissions

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM