Skip to content

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

New issue
New issue
Open
#62063
#61992
Open
[Blazor] Update AuthenticationStateProvider to take advantage of Declarative persistent component state#60718
#62063
#61992
Assignees
ilonatommycopilot-swe-agent
Labels
area-blazorIncludes: Blazor, Razor Components
Milestone
 
.NET 10 Planning
@javiercn

Description

@javiercn
javiercn
opened on 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.

Activity

ghost added
area-blazorIncludes: Blazor, Razor Components
on Mar 3, 2025
javiercn
mentioned this on Mar 3, 2025
javiercn
added this to the .NET 10 Planning milestone on Mar 3, 2025
ilonatommy
self-assigned this
on Apr 4, 2025
ilonatommy
linked a pull request that will close this issue on May 19, 2025
ilonatommy
assigned
Copilot
on May 22, 2025
Copilot
linked a pull request that will close this issue on May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-blazorIncludes: Blazor, Razor Components

Type

No type

Projects

No projects

Milestone

Relationships

None yet

    Development

    Participants

    @javiercn@ilonatommy

    Issue actions
      [Blazor] Update AuthenticationStateProvider to take advantage of Declarative persistent component state · Issue #60718 · dotnet/aspnetcore