Migrate legacy JWT to new asymmetric keys - Self-hosted
self-hostedauth
Solved🟡javascriptHi, anyone know how to get a legacy supabase self-host to use the new asymmetric keys and keep the old anon / server-role keys active? I can't seem to find any docs or info on this. I assume I need to make new jwt keys for sbpublishable and sbsecret , but where to define these for the auth? ( docker or k8s ). Do they just replace the old env variable that anon and service_role use? if so, how to then define the anon and service_role for the deployment to still accept those? Considering I would then need to update my external postgres, and guess all the other services.
Any help or info would be great. thanks!
Any help or info would be great. thanks!
