Dependency AspNetCore.Http in Infra or other project?

I have a situation where I need to have ICurrentUser on both projects

1 - ApplicationCore for any specific rule with user or tenant 2 - Infra - For global filter in dbContext or repository

The implementation of ICurrentUser have a dependency the Microsoft.AspNetCore.Http

For example:

  public class CurrentUser: ICurrentUser
    {
        private readonly IHttpContextAccessor _accessor; //HERE

        public UserSession (IHttpContextAccessor accessor)
        {
            _accessor = accessor;
        }
        public string Name => _accessor.HttpContext.User.Identity.Name;
        public int? TenantId => int.Parse (_accessor.HttpContext.User.Claims.FirstOrDefault (x => x.Type == "TenantId"). ToString ());
        public bool IsAuthenticated => _accessor.HttpContext.User.Identity.IsAuthenticated;
    }

I have as dependency Microsoft.AspNetCore.Http, and need to be used in ApplicationCore and Infra (Data / DbContext)

Would it be correct to leave this implementation and dependency on Infra? Or maybe in another layer (eShopOnWeb.Shared for example)? Where would be the best approach?

Suggestions?

[trevor-hackett]

Place the CurrentUser in the Web project since that is the only project that should know and care about Microsoft.AspNetCore.Http. Keep ICurrentUser in the Core project. Use dependency injection to inject the ICurrentUser into the other projects that need it.

[CESARDELATORRE]

It is ok to have multiple infrastructure projects as long as only the Interfaces/Contracts are the ones defined in the Core project. Then use dependency injection from the application layers (Web project or any other application layer)