Migrating to new asymmetric keys (signing_keys) on local environment.
Hi all,
I am working on the local version of my project before deploying it to production.
I would like to enable the new asymmetric token signing/verification on my local instance, now that this PR is merged: https://github.com/supabase/cli/pull/3841
I have generated the keys with the provided command and then added this line to my
However, when I start my Supabase instance through the CLI, I always get an anon key and service role key, instead of the new public key and secret key.
Is there a way to enable this on the local environment? I am using the latest CLI version 2.33.9.
Thanks
I am working on the local version of my project before deploying it to production.
I would like to enable the new asymmetric token signing/verification on my local instance, now that this PR is merged: https://github.com/supabase/cli/pull/3841
I have generated the keys with the provided command and then added this line to my
config.tomlHowever, when I start my Supabase instance through the CLI, I always get an anon key and service role key, instead of the new public key and secret key.
Is there a way to enable this on the local environment? I am using the latest CLI version 2.33.9.
Thanks
