VRETA

OAuth 2.0

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

Clock skew between our server and the provider makes valid tokens look expired

Our validation logic checks the expiry timestamp against our own clock, and a few seconds of drift is enough to reject a token that has not actually expired from the provider's point of view. Nothing in the token response accounts for skew explicitly. We added a fixed tolerance window as a local fix rather than anything the protocol suggested.
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.