Blazor Server Forces User to Reauthenticate on IIS Recycle / Application Deploy

I started a blazor server project, with the default identity (local account, I think). Allows you to use scaffolding items to edit the identity pages.

Everytime I deploy out an update to IIS, I'm logged out of my application. I would think my bearer token or cookie would still be valid and reestablish a connection no problem.

Every deploy most likely causes an app pool recycle, maybe not since I don't update the web.config.

Anyways, anyone with information on how to keep the token/cookie alive during blazor server deployments would be greatly appreciated. I wasn't finding much luck on the internet.

Googling for answers. Tried looking at identity code to see why this may be the case.

This is usually caused by forgetting to configure a secret-store or key-vault for the server-side code to persist private-keys and other cryptographic details to - which means every time it starts-up it has to re-generate a new set of secrets/private-keys, which invalidate all previously-issued public-keys and signatures.

I'm not a Blazor user so I don't know if Blazor itself requires anything special, but in ASP.NET Core you just need to call AddDataProtection during ConfigureServices and then invoke a data protection implementation on the returned IDataProtectionBuilder, such as:

• PersistKeysToAzureBlobStorage
• ProtectKeysWithCertificate
• PersistKeysToFileSystem