Repository navigation
Derive the Supabase auth cookie name from NEXT_PUBLIC_SUPABASE_URL - #261
Merged
Merged
Conversation
Five API routes read the session cookie by its cloud-derived name sb-xydzwxwsbgmznthiiscl-auth-token. supabase-js names it after the first host label of the project URL, so once the project lives at supabase.qrypt.chat the cookie is sb-supabase-auth-token and those routes would treat every user as logged out. Compute it from the URL instead. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ThreatCrush Security Scan13 finding(s) MEDIUM: 9 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Five API routes (
auth/backup-pin,auth/key-backup,chat/conversations/[id]/participants,crypto/public-keys,crypto/public-keys/all) read the session cookie by the literal namesb-xydzwxwsbgmznthiiscl-auth-token. supabase-js names the cookie after the first host label of the project URL (sb-${hostname.split('.')[0]}-auth-token), so when the project moves to the self-hosted stack athttps://supabase.qrypt.chatthe cookie becomessb-supabase-auth-tokenand these routes would see every user as logged out.src/lib/supabase/auth-cookie.jsnow derives the name fromNEXT_PUBLIC_SUPABASE_URL; the routes and their tests use it. No behaviour change while the URL is still the cloud project.Part of moving qrypt.chat's database onto its own Supabase stack on dev2.
🤖 Generated with Claude Code