In Blazor 9, it seems that AddAuthenticationStateSerialization() and AddAuthenticationStateDeserialization() only work when using ASP.NET Core Identity in the server project (as in the Visual Studio template). For instance, when we intend to use a remote API for authentication with JWT, this automatic persistent serialization does not appear to be helpful. As a result, we need to create a custom AuthenticationStateProvider again to persist the JWT between prerendering and interactive rendering modes.
Since my login page is in prerendering mode, I am looking for JWT storage solutions that do not rely on local storage or cookies.
Does anyone have a suggestion or solution for this?