How to access context outside of hub?

[racamp101]

I need to access the user outside the hub. I can user Context inside the hub just fine but if I try to use IHttpContextAccessor from a class the user is no longer available. Is there another way to get the correct context?

I see posts about injecting IHubContext but I cant access it this way I just need the context.user and using that would cause a circular ref.

[analogrelay]

Have you registered IHttpContextAccessor in the DI container? You have to register it manually: aspnet/Hosting#793

Ah, you mean the User property is not available. I misunderstood.

[analogrelay]

The User property is populated by calling HttpContext.Authentication.AuthenticateAsync. SignalR will call this on your behalf for Hubs with the [Authorize] attribute, as will MVC actions/controllers with the [Authorize] attribute. If you want the user identity in other requests, you need to call it manually. The value is cached as well so it's safe to call it even if SignalR will run later in the middleware pipeline (SignalR will just use the cached value).

[davidfowl]

@racamp101 where are you trying to get access to the user and which user?

[racamp101]

that HttpContext.Authentication.AuthenticateAsync is async saying that sometimes I'm able to access the user is it possible its not finishing sometimes before the method I'm trying to access it in runs?

Im trying to access it in a class that is injected into my hubs constructor.

[davidfowl]

You would need to use the IHttpContextAccessor https://www.strathweb.com/2016/12/accessing-httpcontext-outside-of-framework-components-in-asp-net-core/

[racamp101]

I am using that but the user is only sometimes populated.

[davidfowl]

What transport are you using and how are you asking for the user?

[analogrelay]

that HttpContext.Authentication.AuthenticateAsync is async

Yes, you would need to use it from an async method.

Im trying to access it in a class that is injected into my hubs constructor.

Have you considered passing the data into the service that your hub uses? If the Hub is the one consuming this service, it's the one with access to the user data. The service should accept it as input rather than loading it automatically from an additional dependency. IHttpContextAccessor is only really there as a stop-gap solution when you aren't able to use DI and method parameters to flow the data you need.

[analogrelay]

Closing this as we haven't had any feedback since the last message. Please feel free to comment if you still have questions, we can always re-open or file a new issue if there's a problem to be resolved.

[realLiangshiwei]

I also encountered this problem. When using LongPolling, injecting IHttpContextAccessor in the hub and get user.Claims in httpcontext. sometimes loses information.

[davidfowl]

Don't do that, use the GetHttpContext on the HubConnectionContext.

[realLiangshiwei]

I have defined a global shared session in my architecture. I need to set the value of the session when the request comes.I chose to use IHttpContextAccessor It works fine for mvc and webapi applications,

https://github.com/aspnetboilerplate/aspnetboilerplate/blob/e0ded5d8702f389aa1f5947d3446f16aec845287/src/Abp.AspNetCore/AspNetCore/Runtime/Session/AspNetCorePrincipalAccessor.cs#L11

but the context state is lost in signalr long polling mode. This will result in the correct value not being obtained using a custom session.
var userId = AbpSession.UserId;

Do you have any good solutions?