Skip to main content

Part-2 A Demo On JWT Access Token And Refresh Token Authentication In .NET6 Web API

In this article, we will learn the generation and usage of the refresh token in .NET6 Web API application.

Click here to understand the implementation of the JWT token in .NET6 Web API.

Refresh Token:

When the JWT access token expires to renew it without user credentials we will use the Refresh Token.
Let's understand the flow of  Refresh Token.
  • The user sends valid 'User Name' and 'Password' to the server, then the server will generate JWT Access Token and Refresh Token sent as a response
  • The JWT Access Token is a short live token(eg 20 minutes) and Refresh Token is a long live token(eg: 7 days)
  • Now client application sends a JWT access token in the request header that makes the user authenticated.
  • If the JWT token expires then the server returns 401 unauthorized responses.
  • Then the client sends the refresh token to the server to regenerate the JWT Access token. The server validates the refresh token and returns a new JWT Access Token and a new Refresh Token as a response.

RefreshToken Table SQL Script:

In general Refresh, Token value will be saved into the database. Users can logged-in from multiple devices then we shall have the respective token values so let's create a 'RefreshToken' table. In the 'RefreshToken' table a single user can have multiple tokens based on their authentication from the device.

Note: To remove the expired Refresh Tokens it is advised to run a separate background job so that our table contains only active tokens.

Run the below script to create the 'RefreshToken' table.
CREATE TABLE RefreshToken(
	[Id] [int] IDENTITY(1,1) NOT NULL,
	[UserId] [int] NOT NULL,
	[Token] [varchar](1000) NOT NULL,
	[ExpirationDate] [datetime] NOT NULL,
	[Id] ASC

Create RefreshToken Table Entity And Update DbConte:

Let's create a new class that represents our 'RefreshToken' table.
namespace Dot6.Jwt.API.Data.Entities;

public class RefreshToken
    public int Id { get; set; }
    public int UserId { get; set; }
    public string Token { get; set; }
    public DateTime ExpirationDate { get; set; }
Now register the 'RefreshToken' into our database context class.
using Dot6.Jwt.API.Data.Entities;
using Microsoft.EntityFrameworkCore;

namespace Dot6.Jwt.API.Data;

public class MyAuthContext : DbContext
    public MyAuthContext(DbContextOptions<MyAuthContext> context) : base(context)


    public DbSet<User> User { get; set; }
    public DbSet<RefreshToken> RefreshToken { get; set; }

Create Refresh Token:

Along with JWT Access Token, we also need to generate the Refresh Token whereas the refresh token needs to save into the 'RefreshToken' table.

Let's create a private method in the 'AccountService.cs' file for generating the unique refresh token.
private string CreateRefreshToken()
	var tokenBytes = RandomNumberGenerator.GetBytes(64);
	var refreshtoken = Convert.ToBase64String(tokenBytes);

	var tokenIsInUser = _myAuthContext.RefreshToken
	.Any(_ => _.Token == refreshtoken);

	if (tokenIsInUser)
		return CreateRefreshToken();
	return refreshtoken;
  • (Line: 3&4) Creating the Refresh Token value using the 'RandNumberGenerator'.
  • (Line: 6&7) Cross-check if the newly created refresh token was already in 'RefreshToken'.
  • (Line: 9-12) If the Refresh token already exists in the database then we are going to execute our method(CreateRefreshToken) again.
  • (Line: 13) Returns unique newly created Refresh Token.
Now let's create a private method to save the newly created Refresh Token value per user into the 'RefreshToken' table.
private async Task InsertRefreshToken(int userId, string refreshtoken)
	var newRefreshToken = new RefreshToken
		UserId = userId,
		Token = refreshtoken,
		ExpirationDate = DateTime.Now.AddDays(7)
	await _myAuthContext.SaveChangesAsync();
  • Here save 'UserId', 'RefreshToken', 'Refresh Token Expiration Date' into the 'RefreshToken' table.
Now let's update the 'TokenDto.cs' entity.
namespace Dot6.Jwt.API.Dtos;

public class TokenDto
    public string AccessToken { get; set; }
    public string RefreshToken { get; set; }
  • (Line: 6) Added new property like 'RefreshToken'.
Update the 'GetAuthtokens()' method in the 'AccountService'.
public async Task<TokenDto> GetAuthTokens(LoginDto login)
	User user = await _myAuthContext.User
	.Where(_ => _.Email.ToLower() == login.Email.ToLower() &&
	_.Password == login.Password).FirstOrDefaultAsync();

	if (user != null)
		var accessToken = CreateJwtToken(user);
		var refreshToken = CreateRefreshToken();
		await InsertRefreshToken(user.Id, refreshToken);
		return new TokenDto
			AccessToken = accessToken,
			RefreshToken = refreshToken
	return null;
  • (Line: 10-17) Here along with JWT Access Token, also generating Refresh Token and return in the response
Step 1:

Step 2:

Usage Of Refresh Token:

On JWT Access Token expiration we can use the Refresh Token to renew the JWT Access Token.

Let's create a payload entity like 'RefreshTokenDto.cs'.
namespace Dot6.Jwt.API.Dtos;

public class RefreshTokenDto
    public string Token { get; set; }
Let's define the method definition to renew the JWT Access token in the 'IAccountService.cs'.
Task<TokenDto> RenewTokens(RefreshTokenDto refreshToken);
Let's implement the 'RenewTokens' method into the 'AccountService'.
public async Task<TokenDto> RenewTokens(RefreshTokenDto refreshToken)
	var userRefreshToken = await _myAuthContext.RefreshToken
	.Where(_ => _.Token == refreshToken.Token
	&& _.ExpirationDate >= DateTime.Now).FirstOrDefaultAsync();

	if (userRefreshToken == null)
		return null;

	var user = await _myAuthContext.User
	.Where(_ => _.Id == userRefreshToken.UserId).FirstOrDefaultAsync();


	var newJwtToken = CreateJwtToken(user);
	var newRefreshToken = CreateRefreshToken();

	userRefreshToken.Token = newRefreshToken;
	userRefreshToken.ExpirationDate = DateTime.Now.AddDays(7);
	await _myAuthContext.SaveChangesAsync();

	return new TokenDto
		AccessToken = newJwtToken,
		RefreshToken = newRefreshToken
  • (Line: 3-5) Fetching record from the 'RefreshToken' table.
  • (Line: 7-10) Return empty response if  refresh token is not found in the 'RefreshToken' table
  • (Line: 12&13) Fetching the user information from the 'User' table.
  • (Line: 17&18) Creating new JWT Access Token and Refresh Token.
  • (Line: 20-22) Refresh token need to be used only once, the next new refresh token need to be generated along with the JWT access token. So we have to update our 'RefreshToken' table with the newly generated refresh token value.
  • (Line: 24-28) Returns newly created token as a response.
Let's add the new endpoint for regenerating tokens.
public async Task<IActionResult> RenewTokens(RefreshTokenDto refreshToken)
	var tokens = await _accountService.RenewTokens(refreshToken);
	if (tokens == null)
		return ValidationProblem("Invalid Refresh Token");
	return Ok(tokens);
Step 1:


Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information on generating JWT tokens in .NET6 Web API. I love to have your feedback, suggestions, and better techniques in the comment section below.


  1. Hi,
    thank you for the article.
    I believe in method RenewTokens, you need to add the 7 days to the expiration date on this line:

    userRefreshToken.ExpirationDate = DateTime.Now;


  2. I think you are missing an important part!
    The part missing is how will the RenewTokens' method be called?
    This RenewTokens method needs to be called in a systematical way like with every http request made to the web api or via a background service that is calling the RenewTokens method every n minute.


Post a Comment

Popular posts from this blog

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually

Usage Of CancellationToken In Asp.Net Core Applications

When To Use CancellationToken?: In a web application request abortion or orphan, requests are quite common. On users disconnected by network interruption or navigating between multiple pages before proper response or closing of the browser, tabs make the request aborted or orphan. An orphan request can't deliver a response to the client, but it will execute all steps(like database calls, HTTP calls, etc) at the server. Complete execution of an orphan request at the server might not be a problem generally if at all requests need to work on time taking a job at the server in those cases might be nice to terminate the execution immediately. So CancellationToken can be used to terminate a request execution at the server immediately once the request is aborted or orphan. Here we are going to see some sample code snippets about implementing a CancellationToken for Entity FrameworkCore, Dapper ORM, and HttpClient calls in Asp.NetCore MVC application. Note: The sample codes I will show in

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti