fix(auth): pin OAuth state + sessions to DB regardless of Redis#85
Merged
Conversation
When secondaryStorage is configured Better Auth routes verification (OAuth state, magic-link tokens, email-verify tokens) and sessions through it by default. When Redis hiccups — even briefly — those disappear and OAuth callbacks fail with 'State mismatch: verification not found'. Pin both to the DB: - verification.storeInDatabase: true - session.storeSessionInDatabase: true Redis remains the secondaryStorage backend for rate-limit counters (rateLimit.storage = 'secondary-storage'), which is the original intent of #34. Rate-limit is best-effort cache, OAuth state is not.
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.
Better Auth routes OAuth verification + sessions through secondaryStorage by default when one is configured. Redis hiccup = OAuth callback fails with "State mismatch: verification not found".
verification.storeInDatabase: true— OAuth state, magic-link tokens, email-verify tokens land in Postgressession.storeSessionInDatabase: true— sessions in PostgresRedis remains the rate-limit counter backend (original intent of #34). Rate-limit is best-effort cache; OAuth state is not.