JWKS Empty After Migrating to New Signing Key
Hi everyone,
I recently migrated to a new signing key in Supabase Auth. After the migration, when I visit auth/v1/.well-known/jwks.json, I see that the keys array is empty. I’ve double-checked my setup, and everything seems correct.
Has anyone experienced this before, or does anyone have guidance on what might be causing this issue? Any help would be greatly appreciated!
Thank you!
I recently migrated to a new signing key in Supabase Auth. After the migration, when I visit auth/v1/.well-known/jwks.json, I see that the keys array is empty. I’ve double-checked my setup, and everything seems correct.
Has anyone experienced this before, or does anyone have guidance on what might be causing this issue? Any help would be greatly appreciated!
Thank you!
