Unverified50% confidenceFactExact time
In 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.
1
Sources
50%
Confidence
Long-term
Relevance
9/15/2026
First Seen
Sources
Related Entities
Related Claims
Unverified该鉴权机制本质上是 OAuth 2.0 Bearer Token 模式的简化版本，省去了授权码交换和 Token 刷新等握手流程79% similarUnverifiedConcurrent token refresh without a mutex or single refresh queue mechanism may cause old refresh tokens to be used multiple times and subsequently revoked by the server.76% similarUnverifiedThe agent exchanges the authorization code for an access token at the token endpoint, and after the token expires, it can use a Refresh Token to obtain a new access token without requiring the user to authorize again.70% similarVerifiedThe behavior of frequently switching accounts to circumvent quotas is an abnormal usage pattern from the platform's risk-control perspective and may trigger IP bans, account downgrading, or even account suspension.65% similarUnverifiedBearer Token是OAuth 2.0规范中的标准认证方式，任何持有该令牌的请求方都被视为合法用户62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/923004API
curl https://kongchang.com/api/v1/knowledge/claims/923004MCP
get_claim(id=923004)