feat(oauth2): Token expiry & refresh - #3160
Draft
DerGut wants to merge 1 commit into
Draft
Conversation
DerGut
force-pushed
the
oauth2-token-expiry
branch
from
September 6, 2026 21:19
f1da144 to
4a0a087
Compare
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
1 participant
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.
Which issue does this PR close?
This change is necessary because I'm introducing a cache for contextual sessions in a separate PR. We don't want to return already expired sessions from the cache, so I'm adding refresh behavior first.
What changes are included in this PR?
This PR implements token expiration and refresh for the
OAuth2Managerof theRestCatalog.Are these changes tested?
Thorough unit tests
AI Disclosure
Used help of AI with the changes and tests.