Skip to content

[Blazor] Update AuthenticationStateProvider to take advantage of Declarative persistent component state #60718

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
javiercn opened this issue Mar 3, 2025 · 0 comments · May be fixed by #61992 or #62063
Open

[Blazor] Update AuthenticationStateProvider to take advantage of Declarative persistent component state #60718

javiercn opened this issue Mar 3, 2025 · 0 comments · May be fixed by #61992 or #62063
Assignees
@ilonatommy @Copilot
Labels
area-blazor Includes: Blazor, Razor Components
Milestone
.NET 10 Planning

Comments

@javiercn
Copy link
Member

javiercn commented Mar 3, 2025

Currently this is handled by

aspnetcore/src/Components/WebAssembly/Server/src/AuthenticationStateSerializer.cs

Line 16 in bd1ba76

private readonly Func<AuthenticationState, ValueTask<AuthenticationStateData?>> _serializeCallback;

aspnetcore/src/Components/WebAssembly/WebAssembly.Authentication/src/Services/DeserializedAuthenticationStateProvider.cs

Line 14 in bd1ba76

// Do not change. This must match all versions of the server-side AuthenticationStateSerializer.PersistenceKey.

We want to use the same approach we follow with antiforgery.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ilonatommy ilonatommy

Copilot code review Copilot

Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Milestone
.NET 10 Planning
2 participants
@javiercn @ilonatommy