From f4d3c313a85960c70d73963f33b39205df0f7510 Mon Sep 17 00:00:00 2001 From: maliming Date: Mon, 4 Nov 2024 16:34:14 +0800 Subject: [PATCH] Update configuring-openIddict.md --- docs/en/deployment/configuring-openIddict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/deployment/configuring-openIddict.md b/docs/en/deployment/configuring-openIddict.md index 80fa74d898..30b8078098 100644 --- a/docs/en/deployment/configuring-openIddict.md +++ b/docs/en/deployment/configuring-openIddict.md @@ -36,7 +36,7 @@ To avoid that, consider creating self-signed certificates and storing them in th `AddDevelopmentEncryptionAndSigningCertificate` is disabled in production environment. Signing and encryption of certificates is done using `openiddict.pfx` file in production environment. -You can use the `dotnet dev-certs https -v -ep openiddict.pfx -p 00000000-0000-0000-0000-000000000000` command to generate the `authserver.pfx` certificate. +You can use the `dotnet dev-certs https -v -ep openiddict.pfx -p 00000000-0000-0000-0000-000000000000` command to generate the `openiddict.pfx` certificate. > `00000000-0000-0000-0000-000000000000` is the password of the certificate, you can change it to any password you want.