From a7b57eb8b76bacf5cb418389289ddb512659faa5 Mon Sep 17 00:00:00 2001 From: Muhammad Rashed Otahbashi Date: Sun, 12 Jan 2025 11:58:32 +0200 Subject: [PATCH] Update configuring-openIddict.md solution for deployment issue on IIS --- docs/en/deployment/configuring-openIddict.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/en/deployment/configuring-openIddict.md b/docs/en/deployment/configuring-openIddict.md index 08fcf7d143..e57898e8c6 100644 --- a/docs/en/deployment/configuring-openIddict.md +++ b/docs/en/deployment/configuring-openIddict.md @@ -48,4 +48,6 @@ You can use the `dotnet dev-certs https -v -ep openiddict.pfx -p 00000000-0000-0 > It is recommended to use **two** RSA certificates, distinct from the certificate(s) used for HTTPS: one for encryption, one for signing. +> If you encounter a deployment error on IIS that says "File not found," even though the file exists, consider changing the application pool's advanced settings: set Load User Profile to True, so solve the issue. + For more information, please refer to: https://documentation.openiddict.com/configuration/encryption-and-signing-credentials.html#registering-a-certificate-recommended-for-production-ready-scenarios