From c5939e477bf82f99a337d8b3e4c8dc0ef7397a8f Mon Sep 17 00:00:00 2001 From: Wesley Cabus Date: 2025年10月15日 14:01:42 +0200 Subject: [PATCH 1/2] Add warning when using Redis to store Data Protection keys Added a warning about using Redis cache to store Data Protection keys, since Redis doesn't persist data across service restarts by default. Provided links for configuration guidance. --- .../data-protection/implementation/key-storage-providers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/aspnetcore/security/data-protection/implementation/key-storage-providers.md b/aspnetcore/security/data-protection/implementation/key-storage-providers.md index 1bbce5c8a8e1..fe0c4f3e7b40 100644 --- a/aspnetcore/security/data-protection/implementation/key-storage-providers.md +++ b/aspnetcore/security/data-protection/implementation/key-storage-providers.md @@ -275,6 +275,12 @@ public void ConfigureServices(IServiceCollection services) :::moniker-end +> [!WARNING] +> When using Redis to persist data protection keys, be aware that Redis doesn't persist data by default when restarting. This can cause Data Protection to issue new keys, invalidating previously protected data. +> +> You can configure Redis to enable data persistence to mitigate this: Redis documentation has information on [how to configure persistence](https://redis.io/docs/latest/operate/oss_and_stack/management/persistence/). +> If you're using [Azure Managed Redis](azure/redis/how-to-persistence), ensure you have enabled data persistence. [Azure Cache for Redis](azure/azure-cache-for-redis/cache-how-to-premium-persistence?tabs=premium) needs a premium or higher tier to enable data persistence. + For more information, see the following topics: * [StackExchange.Redis ConnectionMultiplexer](https://github.com/StackExchange/StackExchange.Redis/blob/main/docs/Basics.md) From e9277a4ad35b66f1466265ddc822657903d218c8 Mon Sep 17 00:00:00 2001 From: Wesley Cabus Date: 2025年10月15日 14:16:19 +0200 Subject: [PATCH 2/2] Fix link formatting for Azure Managed Redis documentation --- .../data-protection/implementation/key-storage-providers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/security/data-protection/implementation/key-storage-providers.md b/aspnetcore/security/data-protection/implementation/key-storage-providers.md index fe0c4f3e7b40..2a1c050ac02d 100644 --- a/aspnetcore/security/data-protection/implementation/key-storage-providers.md +++ b/aspnetcore/security/data-protection/implementation/key-storage-providers.md @@ -279,7 +279,7 @@ public void ConfigureServices(IServiceCollection services) > When using Redis to persist data protection keys, be aware that Redis doesn't persist data by default when restarting. This can cause Data Protection to issue new keys, invalidating previously protected data. > > You can configure Redis to enable data persistence to mitigate this: Redis documentation has information on [how to configure persistence](https://redis.io/docs/latest/operate/oss_and_stack/management/persistence/). -> If you're using [Azure Managed Redis](azure/redis/how-to-persistence), ensure you have enabled data persistence. [Azure Cache for Redis](azure/azure-cache-for-redis/cache-how-to-premium-persistence?tabs=premium) needs a premium or higher tier to enable data persistence. +> If you're using [Azure Managed Redis](/azure/redis/how-to-persistence), ensure you have enabled data persistence. [Azure Cache for Redis](/azure/azure-cache-for-redis/cache-how-to-premium-persistence?tabs=premium) needs a premium or higher tier to enable data persistence. For more information, see the following topics:

AltStyle によって変換されたページ (->オリジナル) /