expense-manager | Track your everyday spendings | Data Visualization library

You are attempting to access the user in ExpenseManagerDbContext which is the application’s IdentityDbContext. As such, it itself is a dependency of the authentication system and will get resolved when the framework performs the authentication.

So the flow is somewhat like this:

1. Request comes in.
2. Authentication middleware runs to authenticate the user.
3. UserManager resolves ExpenseManagerDbContext.
4. ExpenseManagerDbContext resolves IGetClaimsProvider.
5. GetClaimsProvider resolves the HttpContext and attempts to access the user’s claims.
6. Authentication middleware performs the authentication and sets HttpContext.User with the result.

If you look at steps 5 and 6, you will see that the HttpContext is accessed before the authentication middleware is able to actually authenticate the user and update the user object on the context. And since the authentication middleware always runs at the beginning of a request, this will always be the case.

I would recommend you to rethink your ExpenseManagerDbContext since it probably shouldn’t depend on the currently signed-in user. It should be independent of that. If you have logic there that depends on the user id, then it should probably be a separate service.