BUG:Update JWT verification to support ES256 with Supabase JWK #275
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
📌 Issue Overview
Updated the JWT verification logic to work with ES256 using the Supabase JWK public key
🔍 Steps to Reproduce
- Switched JWT decoding to ES256 algorithm
- Used JWK public key from Supabase for verification
- Verified token audience as "authenticated"
💡 Result
- Authentication endpoints now work correctly end-to-end
- Frontend requests no longer show
Failed to fetcherrors
Record
- I agree to follow this project's Code of Conduct
- I want to work on this issue