Server-side Blazor: HttpContext is null when new component is created

I’ve got a server-side Blazor / IdentityServer4 / API setup. With every request to the API I’ve got to send the access token that I got from the identity server. I get the access token from the HttpContext when my HttpClient gets created in Startup.cs:

            services.AddHttpClient<IMyClient, MyClient>(client =>
            {
                var serviceProvider = services.BuildServiceProvider();
                var httpContextAccessor = serviceProvider.GetService<IHttpContextAccessor>();

                var task = httpContextAccessor.HttpContext.GetTokenAsync("access_token");
                task.Wait();
                var accessToken = task.Result;

                client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessToken);

                client.BaseAddress = new Uri(Configuration.GetMyApiServerUrl());
            });

Every component, that has to make calls to the API, injects MyClient. If such a component is created, the AddHttpClient function is called and the access token is set for future calls to the API.

This works well on my local machine but on the server, only the first call after page load works. After that, if a new component gets created that injects MyClient, the HttpContext is null inside the AddHttpClient function.

Any idea on how to solve this?

[mihaimyh]

This still is an issue, I can believe there is no official support for this yet since Authentication/Authorization should be considered a priority.

[pranavkm]

@javiercn looks like this hasn’t been resolved as yet - https://github.com/aspnet/AspNetCore/issues/18066. Can you help?