'Need to reboot all instances of a service when creating a new encrpytion key in the keyvault(use IDataProtectionBuilder)
I use the following data protection with protection encryption key:
dataProtectionBuilder.ProtectKeysWithAzureKeyVault(keyUri, tokenCredentials);
If I have a service with 4 instances, for example. When I create a new key version in the Azure keyvault, one instance has been rebooted and thus get the new key version, the other 3 instances still use the old key until they are refreshed from storage(24 hours?). This is a problem. I have to avoid force restart all instances. Is there another way to fix the problem?
Usually for key rotation, we can use both new and old keys for a few days to ensure there is no down time. Is there a way achieve it?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|