Fix intermittent 401 errors and add ES256 JWT support #86

Merged
TheFurya merged 2 commits from feature/fix-intermittent-401-errors into develop 2026-03-22 11:53:52 +01:00
Owner

Summary

  • Proactively refresh Supabase JWT before API calls to prevent expired token 401s
  • Add ES256 (ECC P-256) to accepted JWT algorithms alongside RS256, supporting Supabase's recommended ECC keys
  • Add ES256 test coverage with EC key pair fixtures

Test plan

  • Existing RS256 auth tests pass
  • New ES256 auth test passes
  • Verify authenticated requests succeed with ECC P-256 JWT key in production

🤖 Generated with Claude Code

## Summary - Proactively refresh Supabase JWT before API calls to prevent expired token 401s - Add ES256 (ECC P-256) to accepted JWT algorithms alongside RS256, supporting Supabase's recommended ECC keys - Add ES256 test coverage with EC key pair fixtures ## Test plan - [x] Existing RS256 auth tests pass - [x] New ES256 auth test passes - [ ] Verify authenticated requests succeed with ECC P-256 JWT key in production 🤖 Generated with [Claude Code](https://claude.com/claude-code)
TheFurya added 2 commits 2026-03-22 11:53:32 +01:00
Supabase JWT key was switched to ECC P-256, but the JWKS verification
only accepted RS256. Add ES256 to the accepted algorithms list.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
chore: mark ES256 JWT support bean as completed
All checks were successful
CI / backend-tests (pull_request) Successful in 33s
CI / frontend-tests (pull_request) Successful in 33s
c5959cfd14
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
TheFurya merged commit ce9d08963f into develop 2026-03-22 11:53:52 +01:00
TheFurya deleted branch feature/fix-intermittent-401-errors 2026-03-22 11:53:53 +01:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pokemon/nuzlocke-tracker#86