S

Supabase•3w ago

Amal Chandran

How to access JWT private key/shared secret in Supabase Admin UI

Hi Supabase community,

In local development, I can easily configure custom JWT signing keys using signing_keys_path = "./signing_key.json"signing_keys_path = "./signing_key.json" in config.tomlconfig.toml, which gives me access to the full private key for minting JWTs.

However, in the Supabase dashboard (admin UI), I can only see the public key via the JWKS endpoint (/.well-known/jwks.json/.well-known/jwks.json). I need access to the private key or JWT shared secret in production to match my local setup for custom JWT generation.

I've tried these approaches but they don't work:

• SHOW app.settings.jwt_secret;SHOW app.settings.jwt_secret; (removed from DB)
• SELECT decrypted_secret FROM vault.decrypted_secrets WHERE name = 'app.jwt_secret';SELECT decrypted_secret FROM vault.decrypted_secrets WHERE name = 'app.jwt_secret'; (returns no rows or access denied)
• Old GitHub comment method [https://github.com/supabase/supabase-js/issues/25#issuecomment-683239444]

Is there a dashboard setting, Vault migration step, or CLI command to import/retrieve the private signing key equivalent to local signing_key.jsonsigning_key.json? Or should I generate and import my own signing key pair in production?

Supabase version: latest CLI/dashboard. Local works perfectly with ES256 keys.

Thanks!

GitHub

How to set/get the JWT secret? · Issue #25 · supabase/supabase-js

Question Is there a way to get or set the secret used to sign the JWT access tokens? My use case is to use the Supabase-generated tokens for authorization in other micro-services, so having the sec...