Blazor WASM and IdentityServer4 - AuthenticationState out of sync when using multiple tab pages in chromium

Defect description

We have the following defect when opening our blazor website in multiple chrome tab pages. That when you logout and login a different user in the second tab this isn’t notified in the first tab so the first tab displays the wrong logged-in user and that can make things confusing.

Repro scenario

• Start blazor wasm website with IdentityServer4 as authentication provider
• Open page in tab1 of chrome and login “User 1”
• Open page in tab2 of chrome and see that “User 1” is logged in and logout this user
• No notification in tab1 that user is logged out AuthenticationStateProvider.AuthenticationStateChanged is not triggered
• Try to do something in tab1 gives “Not authorized” because no user logged in

What do I need to change in my configuration so a notification is send to the first tab page that the user was logged out / logged in in a different tabpage in chrome? If there is no out of the box solution for this I might add a custom SignalR event to send this notification.

In my current setup I user the default `builder.Services.AddApiAuthorization();’

[javiercn]

I happen to be working on the IdentityServer4 update, so I’ll give it a quick try to see if there is something easy we can do to enable this.

[msftbot[bot]]

We’ve moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.