Blazor WASM and SSR problem of rendering using authentication

You don't need to define HttpClient where you don't use it.

Consider the WeatherForcast List page.

You can define the data provider for the page like this as an interface.

public interface IWeatherForecastProvider
{
    public Task<ListResult<WeatherForecast>> GetWeatherForecastsAsync(ListRequest request, CancellationToken? cancellationToken = null);
}

The Server version goes straight to the database and gets the data:

public class ServerWeatherForecastProvider : IWeatherForecastProvider
{
    public Task<ListResult<WeatherForecast>> GetWeatherForecastsAsync(ListRequest request, CancellationToken? cancellationToken = null)
    {
        // Dummy singleton provider
        var _provider = WeatherDataProvider.GetInstance();

        var query = _provider.WeatherForecasts
            .Skip(request.StartIndex)
            .Take(request.PageSize);

        var totalCount = query.Count();

        return Task.FromResult(ListResult<WeatherForecast>.Success(query, totalCount));
    }
}

The server API also uses this implementation:

public static void AddAppEndPoints(this WebApplication app)
{
    app.MapPost("/API/Weather/GetWeatherForecasts", async ([FromBody] ListRequest listRequest, IWeatherForecastProvider provider) =>
    {
        var result = await provider.GetWeatherForecastsAsync(listRequest);
        return result;
    });
}

The WASM API version is the only one that uses an HttpContext:

public class APIWeatherForecastProvider : IWeatherForecastProvider
{
    private IHttpClientFactory _httpClientFactory;
    private List<WeatherForecast>? _forecasts;

    public APIWeatherForecastProvider(IHttpClientFactory httpClientFactory)
    {
        _httpClientFactory = httpClientFactory;
    }

    public async Task<ListResult<WeatherForecast>> GetWeatherForecastsAsync(ListRequest request, CancellationToken? cancellationToken = null)
    {
        using var httpClient = _httpClientFactory.CreateClient("ServerAPI");

        var httpResult = await httpClient.PostAsJsonAsync<ListRequest>("/API/Weather/GetWeatherForecasts", request, cancellationToken ?? new());

        if (httpResult.IsSuccessStatusCode)
        {
            var listResult = await httpResult.Content.ReadFromJsonAsync<ListResult<WeatherForecast>>();
            return listResult;
        }
        return ListResult<WeatherForecast>.Failure($"Request failed.  Error Code: {httpResult.StatusCode.ToString()}");
    }
}

The Server Program:

services.AddScoped<IWeatherForecastProvider, ServerWeatherForecastProvider>();

And the WASM Program:

services.AddScoped<IWeatherForecastProvider, APIWeatherForecastProvider>();
services.AddHttpClient("ServerAPI", client => client.BaseAddress = new Uri(baseUrl));

So WebAssembly in "Blazor Web App" seems to be treated differently from what it used to be in a regular WebAssembly project.

What you get is the old WebAssembly NetCore Hosted solution as long as you set Interactivity to Global.

You can see the full solution that this code came from here - https://github.com/ShaunCurtis/Blazr.Auto.Demo