[Blazor Wasm Auth] Single httpclient for both authenticated and non authenticated users

[andersson09]

Is your feature request related to a problem? Please describe.

I do not think it is necessary to have separate http clients for authenticated and non authenticated users (see https://docs.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/additional-scenarios?view=aspnetcore-5.0). The developer has to create a lot of additional code, especially for typed clients.

Describe the solution you'd like

Before sending the request can we check to see if the user is authenticated or not and determine whether to apply the handler logic.

`
Here is a hack to get this working with the current AuthorizationMessageHandler

public class ApiAuthorizationHandler : AuthorizationMessageHandler
{
    private readonly NavigationManager navigation;
    private readonly IConfiguration config;
    private readonly AuthenticationStateProvider authStateProvider;

    //https://github.com/dotnet/aspnetcore/blob/master/src/Components/WebAssembly/WebAssembly.Authentication/src/Services/AuthorizationMessageHandler.cs
    public ApiAuthorizationHandler(IAccessTokenProvider provider, 
        NavigationManager navigation, 
        IConfiguration config,
        AuthenticationStateProvider authStateProvider) : base(provider, navigation)
    {
        this.navigation = navigation;
        this.config = config;
        this.authStateProvider = authStateProvider;
    }

    protected override async Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
    {
        //Hack to bypass handler already configured exception
        var field = this.GetType().BaseType.GetField("_authorizedUris", BindingFlags.Instance | BindingFlags.NonPublic);
        field.SetValue(this, null);

        var authState = await authStateProvider.GetAuthenticationStateAsync();

        if (authState.User.Identity.IsAuthenticated)
        {
            ConfigureHandler(new[]{config.GetValue<string>("ServerUri")});
        }
        else
        {
            //Satisfy validation so that we can call api without needing to be logged in
            ConfigureHandler(new[]{navigation.BaseUri});
        }

        return await base.SendAsync(request, cancellationToken);    
    }
}`

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

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.