Skip to main content

Blazor WebAssembly Custom Authentication From Scratch(Part 2)

In this article, we are going to explore and implement the usage of a refresh token in our Blazor WebAssembly.In Part 1 we have explored complete guidance for implementing authentication in the Blazor WebAssembly application from scratch.

Store Refresh Token In-Browser LocalStorage:

If we recall Part1, we have stored our access token in the browser localStorage, similarly, we need to store our refresh token in the browser localStorage. Now update the 'LoginAsync' method in the AccountService file to save the refresh token.
Services/AccountService:
public async Task<bool> LoginAsync(LoginModel model)
{
  var response = await _httpClient.PostAsJsonAsync<LoginModel>("/account/login-token", model);
  if (!response.IsSuccessStatusCode)
  {
	return false;
  }
  AuthResponse authData = await response.Content.ReadFromJsonAsync<AuthResponse>();
  await _localStorageService.SetItemAsync("token", authData.Token);
  await _localStorageService.SetItemAsync("refreshToken", authData.RefreshToken);
  (_customAuthenticationProvider as CustomAuthenticationProvider).Notify();
  return true;
}
  • (Line: 10) Storing refresh token to browser localStorage.

Try To Access Secured API:

Now we have the access token, now let's try to consume a secured API endpoint from our Blazor WebAssembly application. I have created a test todo endpoint in Jwt Authentication Project(Git link), I will try to consume the 'todo' endpoint from our blazor web application.

Now let's create 'TodoService' files to invoke the API Call.
Services/ITodoService.cs:
using System.Collections.Generic;
using System.Threading.Tasks;
namespace BlazorWasm.JwtAuthLearning.Services
{
  public interface ITodoService
  {
	Task<List<string>> GetTodos();
  }
}
Services/TodoService.cs:
using System.Collections.Generic;
using System.Net.Http;
using System.Net.Http.Headers;
using System.Net.Http.Json;
using System.Threading.Tasks;

namespace BlazorWasm.JwtAuthLearning.Services
{
  public class TodoService:ITodoService
  {
	private readonly HttpClient _httpClient;
	public TodoService(HttpClient httpClient)
	{
		_httpClient = httpClient;
	}

	public async Task<List<string>> GetTodos()
	{
		return await _httpClient.GetFromJsonAsync<List<string>>("/test/todos");
	}
  }
}
  • (Line: 12) Injected HttpClient.
  • (Line: 19) Invoking 'Todo' endpoint.
Now integrate this ITodoService into our Index.razor page, such way on button click we need to invoke this 'Todo' endpoint.
Pages/Index.razor:(Update Authorized Component Part)
<Authorized>
 <h1>Your Dashboard - Your Claims</h1>
 <div>
  <button type="button" class="btn btn-primary" @onclick="Logout">Logout</button>
 </div>
 <div>
  @foreach (var claim in userClaim)
  {
	<div>@claim.Type - @claim.Value</div>
  }
 </div>
 <br/>
 <div>
  @if (todos.Count == 0)
  {
	<div>
		<button type="button" class="btn btn-primary" @onclick="GetTodos">See Your Todos</button>
	</div>
  }
  <ul>
	@foreach (var item in todos)
	{
		<li>@item</li>
	}
  </ul>
 </div>
</Authorized>
  • (Line: 17) Button to invoke the 'Todo' endpoints.
  • (Line: 21-24) Loop and bind the 'Todo' collection.
Inject ITodoService in Index.razor file as below.
Pages/Index.razor:
@inject ITodoService _todoService;
Pages/Index.razor:(Code Part To Invoke Todo API)
@code{
    private List<string> todos = new List<string>();

    private async Task GetTodos()
    {
        todos = await _todoService.GetTodos();
    }
	// code hidden for display purpose
}
Now after login and click on the show todos button will invoke the 'Todo' endpoint which will return the response of UnAuthorized user as below.
The reason behind this unauthorized response, we missed sending the access token as an authorize header to the API call.

Create TokenManagerService:

Now we will create TokenManagerService which provides token all over to the application. In this token manager, we implement steps like fetching token, validating token(expiration), calling refresh token endpoint, etc.
Services/ITokenManagerService.cs:
using System.Threading.Tasks;

namespace BlazorWasm.JwtAuthLearning.Services
{
  public interface ITokenManagerService
  {
   Task<string> GetTokenAsync();
  }
}
Services/TokenManagerService.cs:
using Blazored.LocalStorage;
using BlazorWasm.JwtAuthLearning.Helpers;
using BlazorWasm.JwtAuthLearning.Models;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Net.Http;
using System.Net.Http.Json;
using System.Security.Claims;
using System.Threading.Tasks;

namespace BlazorWasm.JwtAuthLearning.Services
{
  public class TokenManagerService: ITokenManagerService
  {
   private readonly ILocalStorageService _localStorageService;
   public TokenManagerService(ILocalStorageService localStorageService)
   {
	_localStorageService = localStorageService;
   }

   public async Task<string> GetTokenAsync()
   {
	string token =await _localStorageService.GetItemAsync<string>("token");
	return token;
   }
  }
}
  • (Line: 17) Injected ILocalStorageService.
  • (Line: 24) Fetching access token from the browser's local storage.
Update 'Todos' API call in TodoService file to add the access token as authorize header as follows.
Services/TodoService.cs:
private readonly HttpClient _httpClient;
private readonly ITokenManagerService _tokenManagerService;

public TodoService(HttpClient httpClient,
	ITokenManagerService tokenManagerService)
{
  _httpClient = httpClient;
  _tokenManagerService = tokenManagerService;
}

public async Task<List<string>> GetTodos()
{
  string token = await _tokenManagerService.GetTokenAsync();
  _httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("bearer", token);
  return await _httpClient.GetFromJsonAsync<List<string>>("/test/todos");
}
  • (Line: 5) Injected ITokenManagerService
  • (Line: 13) Fetching access token using ITokenManagerService.
  • (Line: 14) Adding token as authorize header to the HttpClient instance.

Now let's try to access Todos API after the expiration of the access token.
The token expiration issue can be resolve by using the refresh token.

Integrate Refresh Token Endpoint:

Now the first thing we need to check whether our access token stored in browser local storage is expired or not. This expiration can be verified by using a claim called 'exp'. So let's create a private method in TokenManagerService to validate the access token expiration as below.
Services/TokenManager.cs:
private bool ValidateTokenExpiration(string token)
{
  List<Claim> claims = JwtParser.ParseClaimsFromJwt(token).ToList();
  if(claims?.Count == 0)
  {
	return false;
  }
  string expirationSeconds = claims.Where(_ => _.Type.ToLower() == "exp").Select(_ => _.Value).FirstOrDefault();
  if (string.IsNullOrEmpty(expirationSeconds))
  {
	return false;
  }

  var exprationDate = DateTimeOffset.FromUnixTimeSeconds(Convert.ToInt64(expirationSeconds));
  if(exprationDate < DateTime.UtcNow)
  {
	return false;
  }
  return true;
}
  • (Line: 1) Passing our access token as an input parameter.
  • (Line: 3) Fetching claims from access token using JwtParser helper class.
  • (Line: 8) Fetching expiration seconds from the 'exp' claim.
  • (Line: 14) Converting expiration seconds to date time.
Now inject the HttpClient object into the TokenManagerService as below.
Services/TokenManagerService:
private readonly HttpClient _httpClient;
private readonly ILocalStorageService _localStorageService;
public TokenManagerService(HttpClient httpClient, ILocalStorageService localStorageService)
{
  _httpClient = httpClient;
  _localStorageService = localStorageService;
}
Now let's create a private method that will invoke the refresh token endpoint.
Models/TokenModel.cs:(Refresh Token Payload Type)
namespace BlazorWasm.JwtAuthLearning.Models
{
  public class TokenModel
  {
   public string Token { get; set; }
   public string RefreshToken { get; set; }
  }
}
Services/TokenManagerService:(Method to call refresh token endpoint)
private async Task<string> RefreshTokenEndPoint(TokenModel tokenModel)
{
  var response = await _httpClient.PostAsJsonAsync<TokenModel>("/account/activate-token-by-refreshtoken", tokenModel);
  if (!response.IsSuccessStatusCode)
  {
	return string.Empty;
  }
  AuthResponse authResponse = await response.Content.ReadFromJsonAsync<AuthResponse>();
  await _localStorageService.SetItemAsync<string>("token", authResponse.Token);
  await _localStorageService.SetItemAsync<string>("refreshToken", authResponse.RefreshToken);
  return authResponse.Token;
}
  • (Line: 3) Invoking refresh token endpoint.
  • (Line: 8) Reading the response data.
  • (Line: 9-10) Storing both new access token and refresh token to browser local storage.
Now update the 'GetTokenAsync' method in TokenManagerService to use the private methods like 'ValidateTokeExpiration()', 'RefreshTokenEndpoint()' as below
Services/TokenManagerService:
public async Task<string> GetTokenAsync()
{
  string token =await _localStorageService.GetItemAsync<string>("token");
  if (string.IsNullOrEmpty(token))
  {
	return string.Empty;
  }

  if (ValidateTokenExpiration(token))
  {
	return token;
  }

  string refreshToken = await _localStorageService.GetItemAsync<string>("refreshToken");
  if (string.IsNullOrEmpty(refreshToken))
  {
	return string.Empty;
  }

  TokenModel tokenModel = new TokenModel { Token = token, RefreshToken = refreshToken };
  return await RefreshTokenEndPoint(tokenModel);
}
  • (Line: 9) Validating access token expiration.
  • (Line: 20) Preparing payload object for refresh token endpoint.
  • (Line: 21) Invoking refresh token endpoint
Now test the 'todo' endpoint after access token expired as below.

That's all about the refresh token integration in blazor webassembly authentication.

Wrapping Up:

Hopefully, I think this article delivered some useful information on the refresh token integration for authentication implementation from scratch in the Blazor WebAssembly application. I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

Popular posts from this blog

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul

GraphQL API Integration In Asp.Net Core Application

Introduction: GraphQL is a query language for your API and a server-side runtime for executing queries by using a type system you define for your data. GraphQL can be integrated into any framework like ASP.NET, Java, NestJs, etc and it isn't tied to any specific database or storage engine and is instead backed by your existing code and data. How GraphQL API Different From Rest API: GraphQL exposes a single end-point or route for the entire application, regardless of its responses or actions. HTTP-POST is the only Http verb recommended by the GraphQL. The client applications (consumers of API) can give instructions to GraphQL API about what type of properties to be returned in the response. Building Blocks Of GraphQL API: The main building blocks of GraphQL API is Schemas and Types.  A 'Schema' in GrpahQL API describes the functionality available to the clients connect to API. Schema mostly consists of GraphQL Object Types, Queries, Mutations, etc. T

ASP.NET Core Web API Versioning

Introduction: An iteration and evolutionary changes of an ASP.NET Core Web API is handled by Versioning. Versioning of an API gives confidence to the clients which consumes API for a long time. Any changes or development of an API will be accessible using the new version and it won't cause issues to the clients consuming the old version of API. When To Use Versioning: Any API response changes. Developing an API by implementing testing levels like 'Alpha', 'Beta', and 'RC' versions before releasing Production. Deprecating an API which means API going to be removed or upgraded by a version within a short period. Versioning Types: Query String Versioning Url Path Versioning Media Type Versioning API Version Nuget: To Configure versioning to AspNet Core Web API Microsoft provided a library(Microsoft.AspNetCore.Mvc.Versioning). So to use the versioning library please install NuGet below.              Install-Package Microsoft.A

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items. The main building block of ion-picker as follows: PickerController PickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker. Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger&quo

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library  jQuery Validate . In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples. Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio. Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as bel

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

Blazor Server CRUD Operations

Introduction: Blazor Server is a web framework to develop server-side single-page applications. Blazor is made up of components with the combinations on C#, Html, CSS.  Blazor Server is production-ready from the .Net Core 3.0.  Blazor Server Working Mechanism: Blazor Server is a very light-weight web development framework.  In Blazor Server, not all code gets downloaded to the client browsers. Blazor Server made of components these components can be a block of code or page with respective navigation.  Blazor server application communicates with the server with a SignalR background connection which is inbuilt functionality. Application click,  form submission, change events, application page navigation every operation is carried out by the SignalR connection by communicating with the server.  Blazor updates the Html DOM very gently on every data update without any overhead. Blazor Server application maintains a nice intelligent tree structure to update the required inform

NestJS API CRUD Operations With MongoDB

Introduction: NestJS is a framework used to develop server-side applications. NestJS built on top of Node.js frameworks like Express. It is a combination of Progressive Javascript, Object-Oriented Programming, Functional Programming, and Functional Reactive Programming. Nest CLI Installation: Using Nest CLI we are able to generate the NestJS starter project with the default template. To install Nest CLI globally over our system open command prompt and run the command               npm i -g @nestjs/cli Now create a sample project by using Nest CLI command              nest new your_project_name package.json: Now open the package.json file from the sample application created, you can observe few properties like "scripts", "dependencies", and "devDependencies". "dependencies" contains all plugins to be installed and used them to run the application. "devDependencies" contain all plugins to be installed and used them

Blazor WebAssembly Dynamic Form Validation

Introduction: In Blazor WebAssembly(client-side framework) form validation can be done with Data Annotations. Using Data Annotations we can validate form either by default validation attributes or by creating custom validation attributes. Using this Data Annotation attribute we can dynamically add or remove validation on a specific field in a form. Create Blazor WebAssembly Project: To create a Blazor WebAssembly template project need to install the latest version of VisualStudio 2019 for rich intelligence support or we can use VisualStudio code but less intelligence support from the editor.  Click here to know about Blazor WebAssembly template creation. Blazor WebAssembly is in preview mode, not yet ready for production. Create Razor Component: After creating a sample project using the Blazor WebAssembly template, in "Pages" folder add new Razor Component , name it as "UserForm.razor" Add Route: In Blazor routing can be configured using @