fix: route standard auth through backend API#22
Draft
shibinsp wants to merge 2 commits into
Draft
Conversation
Make email/password login, signup, and token refresh independent of the frontend Supabase URL so production auth keeps working when Vercel ships a bad browser Supabase config. Keep social sign-in behind a reachable Supabase client and surface a clear warning when that path is unavailable. Fixes #21 Co-Authored-By: Beeax
…ntials - seed_data.py: create Supabase Auth users and set supabase_auth_id so the Supabase-based auth flow resolves seeded accounts; add idempotent --users-only mode that reuses the app engine (Supabase pooler SSL) - README: replace non-existent @taskpulse.demo accounts with the real @acme.com / demo123 seed accounts and document the seed options Refs #21 Co-Authored-By: Beeax
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.
Summary
/api/v1/auth/refreshand restore persisted sessions from stored backend tokensTest plan
cd Frontend && npm run buildcd Frontend && npm run lintcurl -X POST https://relaxed-gates.vercel.app/api/v1/auth/loginwith invalid credentials returns backend401 INVALID_CREDENTIALSinstead of the browser failing on the dead Supabase hostnameFixes #21