Files
nuzlocke-tracker/.beans/nuzlocke-tracker-snft--support-es256-ecc-p-256-jwt-keys-in-backend-auth.md
Julian Tabel fde1867863
All checks were successful
CI / backend-tests (push) Successful in 29s
CI / frontend-tests (push) Successful in 28s
fix: add logging to debug auth issues
2026-03-22 12:01:28 +01:00

721 B

title, status, type, priority, created_at, updated_at
title status type priority created_at updated_at
Support ES256 (ECC P-256) JWT keys in backend auth completed bug normal 2026-03-22T10:51:30Z 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.