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
The theory I have, as discussed on stream, is that the default cookie provider that holds the auth state is encrypted. This key is generated at startup, and a subsequent restart creates a brand new key that cannot decrypt cookies encrypted with the old key. Thus, the state gets invalidated, and users must log in again. Point 4 on this docs page confirms this.
The solution would be to configure Data Protection to persist the key to blob storage or key vault.
No description provided.
The text was updated successfully, but these errors were encountered: