Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

docs: update to reflect changes with rotating legacy secret (#45855)

Taryn Kingde30257ed568
diff --git a/apps/docs/content/troubleshooting/rotating-anon-service-and-jwt-secrets-1Jq6yd.mdx b/apps/docs/content/troubleshooting/rotating-anon-service-and-jwt-secrets-1Jq6yd.mdx
index 71d8384c1a6..4d62b30e58d 100644
--- a/apps/docs/content/troubleshooting/rotating-anon-service-and-jwt-secrets-1Jq6yd.mdx
+++ b/apps/docs/content/troubleshooting/rotating-anon-service-and-jwt-secrets-1Jq6yd.mdx
@@ -26,12 +26,8 @@ If you haven’t migrated to asymmetric JWT signing keys:
{/* supa-mdx-lint-disable Rule004ExcludeWords */}
-1. Go to [**Project Settings** → **JWT Keys**](/dashboard/project/_/settings/jwt) in the Supabase Dashboard
-2. Navigate to the **Legacy JWT Secret** tab
-3. Click on **Change Legacy Secret**
- - Click on **Generate a random secret** to let Supabase decide the JWT secret.
- - Click on **Create my own secret** to enter a custom JWT secret
-4. You will see a Confirmation dialog. Read it through and confirm to proceed.
+We recommend that you migrate to asymmetric JWT signing keys and publishable/secret API keys as it is no longer possible to rotate the legacy anon, service and JWT secrets.
+You can view this [**Get Started guide**](/docs/guides/auth/signing-keys#getting-started) for steps to migrate to asymmetric JWT signing keys.
If you have migrated to new symmetric JWT signing keys: