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
Could someone clarify whether the path for PersistKeys* needs to be unique for each key ring as it wasn't clear from the documentation?
We have been testing the ASP.NET Core DataProtection across several applications which have separate key rings using a shared path (i.e. /data-protection-keys/) and have noticed that we are getting new key.xml files being created before they should. We believe this is due to a cross over in key.xml files for the different key ring when using a shared path for PersistKeys*.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Could someone clarify whether the path for PersistKeys* needs to be unique for each key ring as it wasn't clear from the documentation?
We have been testing the ASP.NET Core DataProtection across several applications which have separate key rings using a shared path (i.e. /data-protection-keys/) and have noticed that we are getting new key.xml files being created before they should. We believe this is due to a cross over in key.xml files for the different key ring when using a shared path for PersistKeys*.
Any help would be greatly appreciated
Beta Was this translation helpful? Give feedback.
All reactions