Minting my own JWTs with JWT Signing Keys - In production
Hey, I've been migrating to JWT signing keys.
In my setup/app I have a crucial requirement to mint my own keys (I did this previsouly with JWT secret). I have it working locally with JWT Signing Keys by generating a key with :
and then in my config.toml
I can use the key in the signing_key.json file to mint my own JWT, and it's all working well locally.
I now need to replicate this in production - How do I import a self generated signing key in production? (equivalent of setting signing_keys_path locally), so i can use JWTs minted with it?
It's mentioned here, but with no further details/instructions
https://supabase.com/docs/guides/auth/signing-keys#how-to-create-mint-jwts-if-access-to-the-private-key-or-shared-secret-is-not-possible
Thanks
Si
In my setup/app I have a crucial requirement to mint my own keys (I did this previsouly with JWT secret). I have it working locally with JWT Signing Keys by generating a key with :
and then in my config.toml
I can use the key in the signing_key.json file to mint my own JWT, and it's all working well locally.
I now need to replicate this in production - How do I import a self generated signing key in production? (equivalent of setting signing_keys_path locally), so i can use JWTs minted with it?
It's mentioned here, but with no further details/instructions
https://supabase.com/docs/guides/auth/signing-keys#how-to-create-mint-jwts-if-access-to-the-private-key-or-shared-secret-is-not-possible
Thanks
Si
Best practices on managing keys used by Supabase Auth to create and verify JSON Web Tokens
