Skip to main content

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

In Par-1 we had implemented a basic angular authentication using the HTTP only cookie. Now we are going to enhance some features like 'Authentication Guard', 'HTTP Interceptor To  Refresh The JWT Token Inside The HTTP Only Cookie', 'User Logout'.

Angular Route Guard For Authentication:

Problem 1:- After successful authentication, we reload our angular application, or the user closes the browser and then opens again, we can see our user information will be lost.

Problem 2:- Currently with our sample application, we can access any page means, if the user is not logged in also can access the 'dashboard' page, similarly if the user logged in can also access the login form page.

Solution:- Implementing Angular  Route Guard for authentication.

In 'AuthService' let's add logic to load the authenticated user information either from the 'AuthService.userProfile' variable or from the browser local storage. Because if the application is reloaded then the info in the 'AuthService.userProfile' will be lost, so in that case, we get authenticated user information from the browser local storage.
src/shared/auth/auth.service.ts:
loadUserFromLocalStorage(): UserModel {
	if (this.userProfile.value.id == 0) {
	  let fromLocalStorage = localStorage.getItem('user-profile');
	  if (fromLocalStorage) {
		let userInfo = JSON.parse(fromLocalStorage);
		this.userProfile.next(userInfo);
	  }
	}
	return this.userProfile.value;
}
Let's create an angular route guard for authentication.
ng g class shared/auth/auth-guard --skip-tests

shared/auth/auth-guard.ts:
import { Injectable } from '@angular/core';
import {
  ActivatedRouteSnapshot,
  CanActivate,
  Router,
  RouterStateSnapshot,
  UrlTree,
} from '@angular/router';
import { Observable } from 'rxjs';
import { AuthService } from './auth.service';

@Injectable()
export class AuthGuard implements CanActivate {
  constructor(private authService: AuthService, private router: Router) {}
  canActivate(
    route: ActivatedRouteSnapshot,
    state: RouterStateSnapshot
  ):
    | boolean
    | UrlTree
    | Observable<boolean | UrlTree>
    | Promise<boolean | UrlTree> {
    let userInfo = this.authService.loadUserFromLocalStorage();
    if (route.data['userType'] === 'guest') {
      return true;
    } else if (route.data['userType'] === 'loged-in') {
      if (userInfo.id > 0) {
        return true;
      }
      this.router.navigate(['/']);
      return false;
    } else if (route.data['userType'] === 'non-loged-in') {
      if (userInfo.id === 0) {
        return true;
      }
      this.router.navigate(['/']);
      return false;
    }
    this.router.navigate(['/']);
    return false;
  }
}
  • (Line: 13) To create a route guard we need to implement 'CanActivate' from the '@angular/router'.
  • (Line: 15-41) The 'canActivate' method gets executed for the routes that got registered with our angular guard in the 'AppRoutingModule'. So if this method returns 'true' then the application loads component respective to the route, if it returns 'false' then the angular application won't allow us to load the component.
  • (Line: 23) Fetching the authenticated user information.
  • (Line: 24-26) The 'route.data['userType']' is a custom property that we will configure in the routes in the 'ApprouteModule', so using this value we can define who can access routes. Here I had implemented value like 'guest' means all can consume the route.
  • (Line: 26-31) The 'logged-in' value means only authentication users can access the route.
  • (Line: 32-38) The 'non-loge-in' value means only users, not logged in can access the route.
Let's register our angular guard and route data in the 'AppModule'.
src/app.module.ts:
import { AuthGuard } from './shared/auth/auth-guard';
// code hidden for display purpose
const routes: Routes = [
  {
    path: '',
    component: HomeComponent,
    canActivate: [AuthGuard],
    data: {
      userType: 'guest',
    },
  },
  {
    path: 'login',
    component: LoginComponent,
    canActivate: [AuthGuard],
    data: {
      userType: 'non-loged-in',
    },
  },
  {
    path: 'dashboard',
    component: DashboardComponent,
    canActivate: [AuthGuard],
    data: {
      userType: 'loged-in',
    },
  },
];
Now register 'AuthGuard' into the providers of 'AppModule'.
src/app.module.ts:
import { AuthGuard } from './shared/auth/auth-guard';
// code hidden for display purpose
@NgModule({
  providers: [AuthGuard],
})
Note:- Now run the application check above mentioned 2 problems and we can observe both of them get resolved.

NestJS Refresh-Token API:

Our NestJS HTTP-Only cookie contains both 'Access Token' and 'Refresh Token'. So if the 'Access Token' expires we have to use 'RefreshToken'. So let's use the 'Refresh-Token' endpoint to regenerate the Cookie with new 'AccessToken' and 'Refresh Token'.
http://localhost:3000/refresh-token

HttpInterceptor To Invoke RefreshToken Endpoint On AccessToken Expires:

Let's implement the logic for Refresh Token API in 'AuthService'.
src/shared/auth/auth.service.ts:
refreshCookie() {
	return this.http.get('http://localhost:3000/refresh-token', {
	  withCredentials: true,
	});
}
Let's create our HttpInterceptor to invoke refresh token endpoint on access token expiration.
ng g class shared/auth/auth.interceptor --skip-tests

src/shared/auth/auth.interceptor.ts:
import {
    HttpEvent,
    HttpHandler,
    HttpInterceptor,
    HttpRequest,
  } from '@angular/common/http';
  import { Injectable } from '@angular/core';
  import { Router } from '@angular/router';
  import { catchError, Observable, switchMap, throwError } from 'rxjs';
  import { AuthService } from './auth.service';
  
  @Injectable()
  export class AuthInterceptor implements HttpInterceptor {
    constructor(private authService: AuthService, private route: Router) {}
  
    intercept(
      req: HttpRequest<any>,
      next: HttpHandler
    ): Observable<HttpEvent<any>> {
      if (req.url.indexOf('/refresh-token') > -1) {
        return next.handle(req);
      }
      return next.handle(req).pipe(
        catchError((error) => {
          if (error.status == 401) {
            return this.handle401Error(req, next, error);
          } else {
            return throwError(() => error);
          }
        })
      );
    }
  
    private handle401Error(
      req: HttpRequest<any>,
      next: HttpHandler,
      originalError: any
    ) {
      return this.authService.refreshCookie().pipe(
        switchMap(() => {
          return next.handle(req);
        }),
        catchError((error) => {
          localStorage.removeItem('user-profile');
  
          this.route.navigate(['/']);
          return throwError(() => originalError);
        })
      );
    }
  }
  • (Line: 13) To create an interceptor we have to implement the 'HttpInterceptor' that loads from the '@angular/common/http'.
  • (Line: 16-32) The 'interceptor()' method gets invoked for every HTTP API request from our angular application.
  • (Line: 20-22) For the refresh token endpoint, we no need to check the user is authenticated or not.
  • (Line: 24-30) The 'catchError' method gets executed for API error response.
  • (Line: 25-27) Checking for 401 status code which means unauthorized exceptions.
  • (Line: 34-50) The 'handle401Error()' method handles the unauthorized exception by invoking the refresh token endpoint, once the new cookie is created, again API's failed will be reinvoked.
Now register our 'AuthInterceptor' into the 'AppModule'.
src/app.module.ts:
import {HTTP_INTERCEPTORS } from '@angular/common/http';
import { AuthInterceptor } from './shared/auth/auth.interceptor';
// code hidden for display purpose
@NgModule({
  providers: [
    {
      provide: HTTP_INTERCEPTORS,
      useClass: AuthInterceptor,
      multi: true,
    },
  ]
})

NestJS Logout API:

Logout API clears the authentication cookie.
http://localhost:3000/logout

Logout In Angular Application:

Let's first add the 'Logout' API call logic in the 'AuthService'.
src/shared/auth/auth.service.ts:
logout() {
    return this.http.get('http://localhost:3000/logout', { withCredentials: true });
}
In 'AppComponent' let invoke the 'Logout' API.
src/app.component.ts:
logOut() {
    this.auth.logout().subscribe({
      next: () => {
        this.auth.userProfile.next({
          email: '',
          firstName: '',
          id: 0,
          lastName: '',
          phone: '',
        });
        localStorage.removeItem('user-profile');
        this.router.navigate(['/']);
      },
    });
}
  • On successful logout API, we have to clear authenticated user information from our angular application like 'auth.userProfile' variable and browser local storage.
let's add the 'SignOut' button on the menu bar.
src/app.component.html:
<li class="nav-item text-dark" (click)="logOut()">
  <button class="btn btn-primary" type="button">SignOut</button>
</li>

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information on JWT Authentication using the HTTP-Only Cookie in Angular application. using I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

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

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

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

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

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

Different HttpClient Techniques To Consume API Calls In Minimal API[.NET6]

In this article, we are going to implement different HttpClient techniques to consume API calls in minimal API. The different HttpClient techniques that we are going to explore are like: Register HttpClient Object Explicitly In DI(Dependency Injection Service) Named Client Type Client HttpRequestMessage Object Create A .NET6 Minimal API Project: Let's create a .Net6 Minimal API sample project 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. CLI command For Minimal API Project dotnet new webapi -minimal -o Your_Project_Name Create A Third Party API Response Model: Here I'm going to use a free third-party rest API that is "https://jsonplaceholder.typicode.com/posts". So to receive the response let's create a response model like 'Post.cs'. Program.cs:(Add Post.cs c

.Net5 Web API Managing Files Using Azure Blob Storage

In this article, we are going to understand the different file operations like uploading, reading, downloading, and deleting in .Net5 Web API application using Azure Blob Storage. Azure Blob Storage: Azure blob storage is Microsoft cloud storage. Blob storage can store a massive amount of file data as unstructured data. The unstructured data means not belong to any specific type, which means text or binary data. So something like images or pdf or videos to store in the cloud, then the most recommended is to use the blob store. The key component to creating azure blob storage resource: Storage Account:- A Storage account gives a unique namespace in Azure for all the data we will save. Every object that we store in Azure Storage has an address. The address is nothing but the unique name of our Storage Account name. The combination of the account name and the Azure Storage blob endpoint forms the base address for each object in our Storage account. For example, if our Storage Account is n

.Net5 Web API Redis Cache Using StackExchange.Redis.Extensions.AspNetCore Library

In this article, we are going to explore the integration of Redis cache in .Net5 Web API application using the 'StackExchange.Redis.Exntensions' library. Note:- Microsoft has introduced an 'IDistributedCache' interface in dotnet core which supports different cache stores like In-Memory, Redis, NCache, etc. It is simple and easy to work with  'IDistributedCache', for the Redis store with limited features but if we want more features of the Redis store we can choose to use 'StackExchange.Redis.Extensions'.  Click here for Redis Cache Integration Using IDistributedCache Interface . Overview On StackExchange.Redis.Extnesions Library: The 'StackExchange.Redis.Extension' library extended from the main library 'StackExchange.Redis'. Some of the key features of this library like: Default serialization and deserialization. Easy to save and fetch complex objects. Search key. Multiple Database Access Setup Redis Docker Instance: For this sampl