fix(studio): refresh OAuth sessions transparently - #926
Merged
yaozheng-fang merged 1 commit intoAug 18, 2026
Conversation
yaozheng-fang
approved these changes
Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/oauth2/userinfo, including refresh-token rotationCompatibility
Existing signed session cookies remain decodable. A legacy cookie containing a refresh token is immediately reissued with the configured absolute session expiry on its next authenticated request. Logout still clears the session, and an expired or revoked refresh token still requires authorization.
Verified both configured providers use refresh-token rotation with a 15-day idle lifetime and a 30-day combined lifetime.
Validation