Repository navigation
Persist Data Protection keys to Azure Blob Storage or Redis - #168
Merged
Merged
Conversation
…ly encrypted with Azure Key Vault Add a DataProtection configuration section selecting the key store (file system by default, Azure Blob Storage or Redis) and an optional Key Vault key that protects the key ring at rest. Contradictory or incomplete settings fail at startup.
This was referenced Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replicas can now share one Data Protection key ring through Azure Blob Storage or Redis instead of a mounted volume, so sessions and tokens survive restarts and load balancing on platforms without shared persistent disks.
Added
Cratis:AuthProxy:DataProtection:Storeselects where the key ring is persisted:FileSystem(the default, still driven byDataProtectionKeysPath),AzureBloborRedis. Azure Blob Storage supports managed identity authentication throughDefaultAzureCredential. Existing deployments are unaffected. (Persist Data Protection keys to a shared store (Azure Blob + Key Vault, Redis) for multi-replica deployments #151)Cratis:AuthProxy:DataProtection:KeyVault:KeyIdentifierencrypts newly generated Data Protection keys with an Azure Key Vault key before storage, in any of the three stores. Existing plaintext keys remain usable and are not retroactively encrypted; existing encrypted keys still require their original vault keys and versions. (Persist Data Protection keys to a shared store (Azure Blob + Key Vault, Redis) for multi-replica deployments #151)AzureBloborRedissection requires selecting that store explicitly rather than leavingStoreat itsFileSystemdefault. (Persist Data Protection keys to a shared store (Azure Blob + Key Vault, Redis) for multi-replica deployments #151)Changed