16 lines
721 B
Markdown
16 lines
721 B
Markdown
---
|
|
# nuzlocke-tracker-snft
|
|
title: Support ES256 (ECC P-256) JWT keys in backend auth
|
|
status: completed
|
|
type: bug
|
|
priority: normal
|
|
created_at: 2026-03-22T10:51:30Z
|
|
updated_at: 2026-03-22T10:59:46Z
|
|
---
|
|
|
|
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.
|
|
|
|
## Summary of Changes\n\nAdded ES256 to the accepted JWT algorithms in `_verify_jwt()` so ECC P-256 keys from Supabase are verified correctly alongside RSA keys. Added corresponding test with EC key fixtures.
|
|
|
|
Deployed to production via PR #86 merge on 2026-03-22.
|