Amir Popovich Amir Popovich - 1 year ago 352
C# Question

JWT Authentication for Asp.Net Web Api

I'm trying to support JWT bearer token (Json Web Token) in my web api application and I'm getting lost.

I see support for

.net core
and for

I'm currently hosting my application over the

How can I achieve this authentication module in my application? Is there any way I can use the
configuration similar to the way I use form's\windows authentication?

Answer Source

I answered this question: How to secure an ASP.NET Web API 4 years ago using HMAC.

Now, lots of things changed in security, esp JWT is getting popular. In here, I will try to explain how to use JWT in the simplest and basic way that I can, so we won't get lost from jungle of OWIN, Oauth2, ASP.NET Identity... :).

If you don't know JWT token, you need to take a look a little bit at:

Basically, a JWT token look like:

<base64-encoded header>.<base64-encoded claims>.<base64-encoded signature>



JWT token has three sections:

  1. Header: JSON format which is encoded as a base64
  2. Claims: JSON format which is encoded as a base64.
  3. Signature: Created and signed based on Header and Claims which is encoded as a base64.

If you use the website with token above, you can see the token like below:

enter image description here

Technically, JWT uses signature which is signed from headers and claims with security algorithm specified in the headers (example: HMACSHA256). Therefore, JWT is required to be transfered over HTTPs if you store any sensitive information in claims.

Now, to use JWT authentication, you don't really need an OWIN middleware if you have legacy Web Api system. The simple concept is how to provide JWT token and how to validate token when the request comes. That's it.

Back to the demo, to keep JWT token lightweight, I only store username and expiration time in JWT. But this way, you have to re-build new local identity (principal) to add more information like: roles.. if you want to do role authorization. But, if you want to add more information into JWT, it's up to you, very flexible.

Instead of using OWIN middleware, you can provide JWT token endpoint using action from controller:

public class TokenController : ApiController
    // This is naive endpoint for demo, it should use Basic authentication to provide token or POST request
    public string Get(string username, string password)
        if (CheckUser(username, password))
            return JwtManager.GenerateToken(username);

        throw new HttpResponseException(HttpStatusCode.Unauthorized);

    public bool CheckUser(string username, string password)
        // should check in the database
        return true;

This is naive action, in production you should use POST request or Basic Authentication endpoint to provide JWT.

How to generate the token based on the username?

You can use the nuget package called System.IdentityModel.Tokens.Jwt from MS to generate the token, or even another package if you like. In the demo, I use HMACSHA256 with SymmetricKey:

    public const string Secret = "856FECBA3B06519C8DDDBC80BB080553"; // your symetric

    public static string GenerateToken(string username, int expireMinutes = 20)
        var symmetricKey = Convert.FromBase64String(Secret);
        var tokenHandler = new JwtSecurityTokenHandler();

        var now = DateTime.UtcNow;
        var tokenDescriptor = new SecurityTokenDescriptor
            Subject = new ClaimsIdentity(new[]
                        new Claim(ClaimTypes.Name, username)

            Expires = now.AddMinutes(Convert.ToInt32(expireMinutes)),

            SigningCredentials = new SigningCredentials(new SymmetricSecurityKey(symmetricKey), SecurityAlgorithms.HmacSha256Signature)

        var stoken = tokenHandler.CreateToken(tokenDescriptor);
        var token = tokenHandler.WriteToken(stoken);

        return token;

The endpoint to provide the JWT token is done, now, how to validate the JWT when the request comes, in the demo I have built JwtAuthenticationAttribute which inherits from IAuthenticationFilter, more detail about authentication filter in here.

With this attribute, you can authenticate any action, you just put this attribute on that action.

public class ValueController : ApiController
    public string Get()
        return "value";

You also can use OWIN middleware or DelegateHander if you want to put JWT validation for your whole WebApi (not specific on Controller or action)

Below is the core method from authentication filter:

    private static bool ValidateToken(string token, out string username)
        username = null;

        var simplePrinciple = JwtManager.GetPrincipal(token);
        var identity = simplePrinciple.Identity as ClaimsIdentity;

        if (identity == null)
            return false;

        if (!identity.IsAuthenticated)
            return false;

        var usernameClaim = identity.FindFirst(ClaimTypes.Name);
        username = usernameClaim?.Value;

        if (string.IsNullOrEmpty(username))
            return false;

        // More validate to check whether username exists in system

        return true;

    protected Task<IPrincipal> AuthenticateJwtToken(string token)
        string username;

        if (ValidateToken(token, out username))
            // based on username to get more information from database in order to build local identity
            var claims = new List<Claim>
                new Claim(ClaimTypes.Name, username)
                // Add more claims if needed: Roles, ...

            var identity = new ClaimsIdentity(claims, "Jwt");
            IPrincipal user = new ClaimsPrincipal(identity);

            return Task.FromResult(user);

        return Task.FromResult<IPrincipal>(null);

The workflow is, using JWT library (nuget package above) to validate JWT token and then return back ClaimsPrincipal. You can perform more validation like check whether user exists on your system and other custom validation if you want. The code to validate JWT token and get principal back:

   public static ClaimsPrincipal GetPrincipal(string token)
            var tokenHandler = new JwtSecurityTokenHandler();
            var jwtToken = tokenHandler.ReadToken(token) as JwtSecurityToken;

            if (jwtToken == null)
                return null;

            var symmetricKey = Convert.FromBase64String(Secret);

            var validationParameters = new TokenValidationParameters()
               RequireExpirationTime = true,
               ValidateIssuer = false,
               ValidateAudience = false,
               IssuerSigningKey = new SymmetricSecurityKey(symmetricKey)

            SecurityToken securityToken;
            var principal = tokenHandler.ValidateToken(token, validationParameters, out securityToken);

            return principal;

        catch (Exception)
            //should write log
            return null;

If the JWT token is validated and principal is return, you should build new local identity and put more information on it to check role authorization if you want.

Remember to add config.Filters.Add(new AuthorizeAttribute()); (default authorization) at global scope in order to prevent any anonymous request to your resources.

You can use Postman to test the demo:

Request token (naive as I mentioned above, just for demo):

GET http://localhost:{port}/api/token?username=cuong&password=1

Put JWT token in the header for authorized request, example:

GET http://localhost:{port}/api/value

Authorization Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1bmlxdWVfbmFtZSI6ImN1b25nIiwibmJmIjoxNDc3NTY1MjU4LCJleHAiOjE0Nzc1NjY0NTgsImlhdCI6MTQ3NzU2NTI1OH0.dSwwufd4-gztkLpttZsZ1255oEzpWCJkayR_4yvNL1s

I put my demo in here:

Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download