From 5e3518ffd6c8dba13b94e4ab4c37c19d2095ceaf Mon Sep 17 00:00:00 2001 From: Han Qiao Date: Fri, 1 Aug 2025 22:00:52 +0800 Subject: [PATCH] docs: use the correct command for generating signing key (#37623) --- apps/docs/content/guides/auth/signing-keys.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/guides/auth/signing-keys.mdx b/apps/docs/content/guides/auth/signing-keys.mdx index 1810a3861f7..6532cf7341e 100644 --- a/apps/docs/content/guides/auth/signing-keys.mdx +++ b/apps/docs/content/guides/auth/signing-keys.mdx @@ -171,7 +171,7 @@ If you wish to make your own JWTs or have access to the private key or shared se Use the [Supabase CLI](/docs/reference/cli/introduction) to quickly and securely generate a private key ready for import: ```sh -supabase gen generate-key ES256 +supabase gen signing-key --algorithm ES256 ``` Make sure you store this private key in a secure location, as it will not be extractable from Supabase.