feat: use Supabase Auth sessions for hosted accounts - #6
Merged
Merged
Conversation
Defiabell
changed the title
Defiabell
marked this pull request as ready for review
September 20, 2026 02:44
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.
Hosted login currently performs local password hashing in the Worker and exceeds the free CPU budget. This change moves password handling and browser sessions to a dedicated Supabase Auth project, while retaining ShotSync's account limits, recovery codes, device tokens and file quotas in D1.
Access JWTs stay in browser memory; refresh tokens use a Secure/HttpOnly cookie. The Worker verifies cached asymmetric JWKS, account namespace, authentication version and session revocation. Logout immediately blocks existing JWTs; recovery blocks old JWTs/devices before updating the provider. Website registration still checks Turnstile and the atomic 100-account cap before admin creation, so public Supabase signup remains disabled. Ambiguous registration/recovery mutations fail closed for operator reconciliation.
Default self-hosting remains Worker + R2 + AUTH_TOKEN, without accounts, D1 or Supabase. Migration 0004 preserves existing data; legacy hosted accounts require their recovery code. README and operator documentation explain both modes and rollout limits.
Validation: Worker/D1/R2 unit and browser tests, typecheck, deployment dry-run, independent security review, and real personal Supabase integration (ES256 login, refresh, logout, and same-password recovery rejecting the old refresh token). Production CPU must be measured after rollout; mock tests do not establish free-plan capacity. No paid upgrade.