feature: use redis for refresh lock if available#959
Open
mattdjenkinson wants to merge 8 commits into
Open
Conversation
mattdjenkinson
changed the title
yahyafakhroji
previously approved these changes
Feb 3, 2026
kevwilliams
previously approved these changes
Feb 3, 2026
yahyafakhroji
force-pushed
the
feature/895-use-redis-for-rate-limit-and-refresh-lock
branch
from
d84b5a1 to
bd891e5
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
3 participants
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.
This PR adds the ability for the session refresh token lock to be stored in Redis, giving us multi pod resiliency.
Issue: #895
Testing Locally
Token Refresh Lock:
