From ea38f1b67ec4f6feeebec10bbff351b93e3e43a5 Mon Sep 17 00:00:00 2001 From: OpenIddict Bot <32257313+openiddict-bot@users.noreply.github.com> Date: Thu, 13 Oct 2022 14:41:31 +0000 Subject: [PATCH] Update the documentation pages --- configuration/encryption-and-signing-credentials.html | 4 ++++ manifest.json | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/configuration/encryption-and-signing-credentials.html b/configuration/encryption-and-signing-credentials.html index 356c82c..1e534a9 100644 --- a/configuration/encryption-and-signing-credentials.html +++ b/configuration/encryption-and-signing-credentials.html @@ -135,6 +135,10 @@ Unlike ephemeral keys, development certificates are persisted - but not shared a
This feature is not available on .NET Framework 4.6.1: calling options.AddDevelopmentEncryptionCertificate()
or options.AddDevelopmentSigningCertificate()
will result in a PlatformNotSupportedException
being thrown at runtime if no valid development certificate can be found and a new one must be generated.
options.AddDevelopmentEncryptionCertificate()
or options.AddDevelopmentSigningCertificate()
cannot be used in applications deployed on IIS or Azure App Services:
+trying to use them on IIS or Azure App Services will result in an exception being thrown at runtime (unless the application pool is configured to load a user profile).
+To avoid that, consider creating self-signed certificates and storing them in the X.509 certificates store of the host machine(s).
To register a signing or encryption key, an instance of a SecurityKey
- typically a SymmetricSecurityKey
or a RsaSecurityKey
-
can be provided to the options.AddSigningKey()
/options.AddEncryptionKey()
methods: