Skip to main content

Hot Chocolate GraphQL Custom Authentication Series Using Pure Code First Technique - Part4 - Refresh Token

Part3 we had enabled the JWT token validation and discussed different authorization techniques as well. In this article, we will understand Refresh Token creation and its usage.

When To Use Refresh Token:

A refresh token is a unique random encrypted string. On the expiration of the JWT auth access token, instead of showing a login page to the user, we can make the user authenticated immediately using the refresh token. By using refresh token we can fetch new user access tokens from the server without any user credentials.

Generate Refresh Token:

In 'AuthLogic.cs' file add a new private method like 'GenerateRefreshToken()'.
Logics/AuthLogics.cs:
private string GenerateRefreshToken()
{
	var randomNumber = new byte[32];
	using (var generator = RandomNumberGenerator.Create())
	{
		generator.GetBytes(randomNumber);
		return Convert.ToBase64String(randomNumber);
	}
}
  • Here using 'System.Security.Cryptography.RandomNumberGenerator' generated refresh token of length 32bytes. 
Recall Part2 where we have a public method like 'Login' to generate the access token. Currently, we just return access token from this method so it's return type 'String'. Now along with the JWT Access Token, we have to return Refresh Token as well. So let's creates like 'Models' and add a new class like 'TokenResponseModel.cs'.
Models/TokenResponseModel.cs:
namespace GraphQL.PureCodeFirst.Auth.Models
{
    public class TokenResponseModel
    {
        // Message property helps to serve validation errors to client
        public string Message{get;set;}
        public string AccessToken { get; set; }
        public string RefreshToken { get; set; }
    }
}
Let's update our 'Login()' method to return 'TokenResponseModel' as output.
Logics/AuthLogic.cs:
public TokenResponseModel Login(LoginInputType loginInput)
{
	var result = new TokenResponseModel{Message = "Success"};
	if (string.IsNullOrEmpty(loginInput.Email)
	|| string.IsNullOrEmpty(loginInput.Password))
	{
		 result.Message = "Invalid Credentials";
		 return result;
	}

	var user = _authContext.User.Where(_ => _.EmailAddress == loginInput.Email).FirstOrDefault();
	if (user == null)
	{
		result.Message =  "Invalid Credentials";
		return result;
	}

	if (!ValidatePasswordHash(loginInput.Password, user.Password))
	{
		result.Message =  "Invalid Credentials";
		return result;
	}

	var roles = _authContext.UserRoles.Where(_ => _.UserId == user.UserId).ToList();

	result.AccessToken =  GetJWTAuthKey(user, roles);

	result.RefreshToken  = GenerateRefreshToken();

	user.RefreshToken = result.RefreshToken;
	user.RefershTokenExpiration = DateTime.Now.AddDays(7);
	_authContext.SaveChanges();

	return result;
}
  • (Line: 3) Initialized 'TokenResponseModel' object.
  • (Line: 28) Generating the Refresh Token.
  • (Line: 30-32) Saving refresh token and its expiration to 'User' table.
Since our 'Login()' method return type changed, we have to update in 'IAuthLogic' as well.
Logics/IAuthLogic.cs:
TokenResponseModel Login(LoginInputType loginInput);
Also, update our 'Login' resolver in the 'MutationResolver.cs' file.
Resolvers/MutationResolver.cs:
public TokenResponseModel Login([Service] IAuthLogic authLogic,LoginInputType loginInput)
{
	return authLogic.Login(loginInput);
}
Let's frame mutation for login.
Mutation:
mutation($MyLogin:LoginInputTypeInput){
  login(loginInput:$MyLogin){
    message,
    accessToken,
    refreshToken
  }
}
Variable:
{
  "MyLogin":{
      "email":"test@test.com",
      "password":"Test@1234"
  }
}

Refresh Token Working Flow:

Let's understand the refresh token working flow:
  • On the expiration of our JWT access token, the client app should renew the access token by using the refresh token.
  • So the client app will send the refresh token and expired access token to the server.
  • The server application decodes our expired access token and fetches the claims inside of it.
  • Now using email claim and refresh token we should query the 'User' table.
  • If a user record founds then we will create a new access token and a new refresh token as well.
  • The best practice is to use a refresh token only once, always try to create a new refresh token along with a JWT access token.

Implement Access Token Renewal Logic Using Refresh Token:

Let's create a private method like 'GetClaimsFromExpiredToken()'. This method contains logic to fetch claims from the expired token.
Logics/AuthLogic.cs:
private ClaimsPrincipal GetClaimsFromExpiredToken(string accessToken)
{
	var tokenValidationParameter = new TokenValidationParameters
	{
		ValidIssuer = _tokenSettings.Issuer,
		ValidateIssuer = true,
		ValidAudience = _tokenSettings.Audience,
		ValidateAudience = true,
		IssuerSigningKey = new SymmetricSecurityKey(Encoding.UTF8.GetBytes(_tokenSettings.Key)),
		ValidateLifetime = false // ignore expiration
	};

	var jwtHandler = new JwtSecurityTokenHandler();
	var principal = jwtHandler.ValidateToken(accessToken, tokenValidationParameter, out SecurityToken securityToken);

	var jwtScurityToken = securityToken as JwtSecurityToken;
	if (jwtScurityToken == null)
	{
		return null;
	}

	return principal;
}
  • (Line: 3-11) Initialize 'TokenValidationParameters' object. The 'ValidateLifetime' must set to false because here our target to decrypt the expired token.
  • (Line: 13-14) Using the 'JwtSecurityTokenHandler' instance we will validate our expired access token and finally generates claims.
Now we have to create a  payload object in the 'InputTypes' folder like 'RenewTokenInputType.cs'.
InputTypes/RenewTokenInputType.cs:
namespace GraphQL.PureCodeFirst.InputTypes
{
    public class RenewTokenInputType
    {
        public string AccessToken { get; set; }
        public string RefreshToken { get; set; }
    }
}
Now let's create a public method like 'RenewAccessToken()' that contains all core logic to generate a new jwt access token and refresh token.
Logics/AuthLogic.cs:
public TokenResponseModel RenewAccessToken(RenewTokenInputType renewToken)
{
	var result = new TokenResponseModel { Message = "Success" };

	ClaimsPrincipal principal = GetClaimsFromExpiredToken(renewToken.AccessToken);

	if (principal == null)
	{
		result.Message = "Invalid Token";
		return result;
	}
	string email = principal.Claims.Where(_ => _.Type == "Email").Select(_ => _.Value).FirstOrDefault();
	if (string.IsNullOrEmpty(email))
	{
		result.Message = "Invalid Token";
		return result;
	}

	var user = _authContext.User
	.Where(_ => _.EmailAddress == email && _.RefreshToken == renewToken.RefreshToken && _.RefershTokenExpiration > DateTime.Now).FirstOrDefault();
	if (user == null)
	{
		result.Message = "Invalid Token";
		return result;
	}

	var userRoles = _authContext.UserRoles.Where(_ => _.UserId == user.UserId).ToList();

	result.AccessToken = GetJWTAuthKey(user, userRoles);

	result.RefreshToken = GenerateRefreshToken();

	user.RefreshToken = result.RefreshToken;
	user.RefershTokenExpiration = DateTime.Now.AddDays(7);

	_authContext.SaveChanges();

	return result;

}
  • (Line: 5) Trying to fetch the claims from the expired jwt access token.
  • (Line: 12) Trying to fetch user email from the user claims.
  • (Line: 19-25) Fetching a user record from the database by filtering with email, refresh token, and refresh token expiration values.
  • (Line: 27) Fetching roles from the 'UserRoles' table.
  • (Line: 29) Fetching new jwt access token.
  • (Line: 31) Generating the new refresh token.
  • (Line: 33-34) Saving refresh token and refresh token expiration new values to the database.
In the 'IAuthLogic.cs' file add the abstract method. 
Logics/IAuthLogic.cs:
TokenResponseModel RenewAccessToken(RenewTokenInputType renewToken);
Let's create a resolver method for the renewal of tokens in the 'MutationResolver.cs' file.
Resolvers/MutationResolver.cs:
public TokenResponseModel RenewAccessToken([Service] IAuthLogic authLogic,RenewTokenInputType renewToken)
{
	return authLogic.RenewAccessToken(renewToken);
}
Let's frame the mutation.
Mutation:
mutation($RenewToken:RenewTokenInputTypeInput){
  renewAccessToken(renewToken:$RenewToken){
     message,
    accessToken,
    refreshToken
  }
}
Variable:
{
  "RenewToken":{
    "accessToken":"your expired access token value",
    "refreshToken":"refresh token value"
  }
}
That's all about the usage of the Refresh Token.

Video Session:

 

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information on Refresh Token to renew the expired JWT Access Token in the Pure Code First technique in Hot Chocolate GraphQL. I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

Popular posts from this blog

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'

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update 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 the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the 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 the authentication with HTTP-only JWT cookie then we no need to implement the 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 authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G

.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 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

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

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

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot

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