-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Introduce a read-only mode for data protection keyring consumers #53539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
When multiple app instances consume the same keyring, they all try to rotate it, leading to races. This change introduces an IConfiguration property (usually set as an env var) that puts data protection in a read-only mode. The expectation is that writing will be done by a separate (i.e. non-app-instance) component. Part of dotnet#52915
Chris pointed out that |
src/DataProtection/DataProtection/src/Internal/KeyManagementOptionsPostSetup.cs
Show resolved
Hide resolved
src/DataProtection/DataProtection/src/Internal/KeyManagementOptionsPostSetup.cs
Outdated
Show resolved
Hide resolved
Co-authored-by: Chris Ross <[email protected]>
...test/Microsoft.AspNetCore.DataProtection.Tests/Internal/KeyManagementOptionsPostSetupTest.cs
Show resolved
Hide resolved
Interesting - the failure is specific to *nix. Investigating. |
/backport to branch release/8.0 |
Started backporting to branch: https://github.com/dotnet/aspnetcore/actions/runs/8088872298 |
@amcasey an error occurred while backporting to branch, please check the run log for details! Error: The specified backport target branch branch wasn't found in the repo. |
/backport to release/8.0 |
Started backporting to release/8.0: https://github.com/dotnet/aspnetcore/actions/runs/8088881925 |
Introduce a read-only mode for data protection keyring consumers
Description
When multiple app instances consume the same keyring, they all try to rotate it, leading to races. This change introduces an IConfiguration property (usually set as an env var) that puts data protection in a read-only mode. The expectation is that writing will be done by a separate (i.e. non-app-instance) component.
Fixes #52915