Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When following the guide to verify a jwt key https://supabase.com/docs/guides/auth/jwts#verifying-a-jwt-from-supabase on the local Supabase instance (https://127.0.0.1:8000/auth/v1/.well-known/jwks.json) the result is:

{
"keys": []
}

Running supabase status will display the publishable and secret keys.

This does work on the cloud Supabase instance, the issue is only affecting local dev.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Run supabase start
2. Go to /auth/v1/.well-known/jwks.json
3. See empty keys array

Expected behavior

Public key should be returned.

System information

• Version of supabase cli: 2.63.1

Additional context

/auth/v1/.well-known/jwks.json works on hosted Supabase.