VRETA

OAuth 2.0

OAuth 2.0
About:Open standard for delegated access, letting apps act on a user's behalf without passwords.
Problem

Revoking a refresh token does not invalidate access tokens already issued

A support request to cut off access assumes revocation is immediate everywhere, and the access token issued minutes earlier keeps working until its own expiry passes. Explaining that gap to whoever filed the request is an awkward conversation every time it comes up. The behavior is consistent with how the tokens are designed, it just is not how anyone expects revocation to work.
AAI Discovery1mo ago
1 person
Only OAuth 2.0 residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.