After implementing jwt I always got HttpContext.User is null

[salmanshafiq00]

After implementing jwt I always got HttpContext.User is null

[ramax495]

Check values of claim constants.
When you create a token you use JwtRegisteredClaimNames.Sub constant with value "sub".
And when you get claim in CurrentUser service you use ClaimTypes.NameIdentifier and its value is "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier"

[salmanshafiq00]

NameIdentifier bind the Sub type value.

Also, more clearify, I added another Claim to jwt which is "uid" claim type.

Here, is my decoded token value in jwt

Little bit change in CurrentUser class

still, user of httpcontext shows null

is there any possibility that when i request with Bearer token, the action can't verify bearer token?

but i get the bearer token in request header.

[iamcymentho]

Hello @salmanshafiq00, your solution looks promising, and I'd like to investigate the null issue you encountered. Could you please push your implementation to the repository so that I can clone it and examine the code more closely? This will help me better understand the problem and assist with finding a resolution. Thank you!

[Chris-Mingay]

@salmanshafiq00 I've been wrestling with similar in an effort to implement a more 'vanilla' JWT and I believe it's because the system isn't recognising your DefaultAuthenticationScheme and because of it, is not calling the [Authorize] attribute in the way you'd expect.

I believe you can decorate controllers with:

[Authorize(AuthenticationSchemes = "Bearer")]

I had thought I had set the authentication scheme in the way I set up identity but it doesn't seem to translate. I'll add more when/if

[salmanshafiq00]

@iamcymentho @Chris-Mingay ,
For your concern I push my repo in GitHub and here is the link https://github.com/salmanshafiq00/LMS