From b22bd5691d03cd45d3b630f662f05d1b14865770 Mon Sep 17 00:00:00 2001 From: David Klempfner Date: Fri, 29 Sep 2023 15:48:35 +1000 Subject: [PATCH] Update automatic_key_management.md Fixed typos. --- .../content/fundamentals/keys/automatic_key_management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/IdentityServer/v6/docs/content/fundamentals/keys/automatic_key_management.md b/IdentityServer/v6/docs/content/fundamentals/keys/automatic_key_management.md index 44df54ca..fac46b0a 100644 --- a/IdentityServer/v6/docs/content/fundamentals/keys/automatic_key_management.md +++ b/IdentityServer/v6/docs/content/fundamentals/keys/automatic_key_management.md @@ -86,8 +86,8 @@ that should be encrypted at rest. By default, keys managed by Automatic Key Management are protected at rest using ASP.NET Core Data Protection. This is controlled with the *DataProtectKeys* flag, which is on by default. We recommend leaving this flag on unless you are using a custom *ISigningKeyStore* to store -you keys in a secure location that will ensure keys are encrypted at rest. For -example, if you implement the *ISigningKeyStore* to store you keys in Azure Key +your keys in a secure location that will ensure keys are encrypted at rest. For +example, if you implement the *ISigningKeyStore* to store your keys in Azure Key Vault, you could safely disabled *DataProtectKeys*, relying on Azure Key Vault to encrypt your signing keys at rest.