feat: use personal access tokens for long-lived auth - #7
Merged
Merged
Conversation
Exchange short-lived Supabase JWT for a long-lived PAT after OAuth login. PATs never expire unless revoked, fixing the 1-hour logout issue. - Add pat field to Credentials with backward-compatible serde defaults - Exchange Supabase tokens for PAT via POST /tokens/cli after OAuth - Use PAT in Authorization header when available - Skip token refresh logic when using PAT - On 401 with PAT, clear credentials and prompt re-login - Fix TOKEN_LIFETIME to 3600s (was incorrectly 28800s) - Add rust-analyzer to nix dev shell
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.
Summary
Exchange short-lived Supabase JWT for a long-lived PAT after OAuth login. PATs never expire unless revoked, fixing the 1-hour logout issue.
Changes
How to test
Checklist
cargo build --workspace)cargo test --workspace)