Blazor WASM: logout when got 401, should i expect logout to be run when call

[ghostinside]

the page has an attribute [Authorize] the app covered with CascadingAuthenticationState

when I call an external API I intercept the response to check if it is 401, if so, raise an Unauthorized exception & catch it

catch (UnauthorizedAccessException)
{
Console.WriteLine("UnauthorizedAccessException catch");
_authenticationStateProviderBase.Logout();
}

I expected the Blazor to redirect to logout when

_authenticationStateProviderBase.Logout();

public override void Logout()
{
Console.WriteLine("logout");
NotifyAuthenticationStateChanged(GetAuthenticationStateAsync());
}

and the user is not authenticated anymore, but nothing happens, should I use the navigation manager logout instead?

[ghostinside]

is it ok to try to get

AuthenticationStateProvider.AuthenticationStateChanged += AuthenticationStateProviderOnAuthenticationStateChanged;

from

@Inject AuthenticationStateProvider AuthenticationStateProvider

??? does not work, the service is scoped, but even having in app.razor

protected override Task OnInitializedAsync()
{
Console.WriteLine("AuthenticationStateProviderOnAuthenticationStateChanged | OnInitializedAsync");
Console.WriteLine(AuthenticationStateProvider.GetType().ToString());
AuthenticationStateProvider.AuthenticationStateChanged += AuthenticationStateProviderOnAuthenticationStateChanged;

return base.OnInitializedAsync();

}

does not fire an event when i manually call

_authenticationStateProvider.Logout();

[ghostinside]

finally did through handler

`public class CustomDelegatingHandler(NavigationManager navm, IConfiguration config) : DelegatingHandler
{
protected override async Task SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
{
request.SetBrowserRequestCredentials(BrowserRequestCredentials.Include);
var response = await base.SendAsync(request, cancellationToken);
if (response.StatusCode == HttpStatusCode.Unauthorized)
{
Console.WriteLine("CustomDelegatingHandler | SendAsync | HttpStatusCode.Unauthorized");

        navm.NavigateTo(config["Identity:LoginPath"]);
    }
    return response;
}

}`

hope if i create control & place it to page & inject auth state service to the control, it will work, but needs to be checked