Unverified50% confidenceFactExact time
The OAuth 2.0 specification defines a standard Token Revocation interface in RFC 7009, allowing clients to actively revoke tokens.
1
Sources
50%
Confidence
Long-term
Relevance
9/22/2026
First Seen
Sources
Related Entities
Related Claims
Unverified该鉴权机制本质上是 OAuth 2.0 Bearer Token 模式的简化版本，省去了授权码交换和 Token 刷新等握手流程78% similarUnverifiedIn OAuth 2.0, after a refresh token is revoked, the access tokens issued by it should theoretically also become invalid, but in practice this propagation often depends on an additional revocation list mechanism.76% similarUnverifiedBearer Token是OAuth 2.0规范中的标准认证方式，任何持有该令牌的请求方都被视为合法用户68% similarUnverifiedOAuth tokens can be revoked at any time; users can immediately revoke a token on the authorization server side to cut off an agent's access without affecting the user's own account.66% similarUnverifiedRFC 7592 defines the Client Registration Management Protocol, which allows subsequent updates and deletions of already-registered clients.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/940936API
curl https://kongchang.com/api/v1/knowledge/claims/940936MCP
get_claim(id=940936)