You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jtheisen Yea the race condition comment embedded in that question is exactly what I was on about here. Last time I looked at the code, it made no attempt to deal with a race. I think they've left it on the library user to designate a primary responsible for rotating keys and all others are readers. When deploying to a scale set like the domain joined ref arch, this would require leader election, and it all gets unnecessarily complex.
Does the ASP.NET code actually do anything to deal with multiple processes attempting to create/rotate keys simultaneously?
https://docs.microsoft.com/en-us/aspnet/core/security/data-protection/implementation/key-storage-providers?view=aspnetcore-2.2
I think it does not:
https://docs.microsoft.com/en-us/aspnet/core/security/data-protection/configuration/overview?view=aspnetcore-2.2#disableautomatickeygeneration
The text was updated successfully, but these errors were encountered: