nuzlocke-tracker/.beans/nuzlocke-tracker-snft--support-es256-ecc-p-256-jwt-keys-in-backend-auth.md at e935bc4d32c0b95794e12c2f484820e85f4db99e

Files

Julian Tabel e935bc4d32 fix: accept ES256 (ECC P-256) JWT keys alongside RS256 in backend auth

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>

2026-03-22 11:52:42 +01:00

440 B

Raw Blame History

title, status, type, created_at, updated_at

title	status	type	created_at	updated_at
Support ES256 (ECC P-256) JWT keys in backend auth	in-progress	bug	2026-03-22T10:51:30Z	2026-03-22T10:51:30Z

Backend JWKS verification only accepts RS256 algorithm, but Supabase JWT key was switched to ECC P-256 (ES256). This causes 401 errors on all authenticated requests. Fix: accept both RS256 and ES256 in the algorithms list, and update tests accordingly.

440 B Raw Blame History

440 B

Raw Blame History