Julian Tabel
e935bc4d32
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>
11 lines
440 B
Markdown
11 lines
440 B
Markdown
---
|
|
# nuzlocke-tracker-snft
|
|
title: Support ES256 (ECC P-256) JWT keys in backend auth
|
|
status: in-progress
|
|
type: bug
|
|
created_at: 2026-03-22T10:51:30Z
|
|
updated_at: 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.
|