15

Node.js + Angular 11: JWT Authentication & Authorization example

 3 years ago
source link: https://dev.to/bezkoder/node-js-angular-11-jwt-authentication-authorization-example-4add
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Cover image for Node.js + Angular 11: JWT Authentication & Authorization example

Node.js + Angular 11: JWT Authentication & Authorization example

Dec 19

・3 min read

In this tutorial, we will learn how to build a full stack Node.js Express + Angular 11 Authentication example. The back-end server uses Node.js Express with jsonwebtoken for JWT Authentication & Authorization, Sequelize for interacting with MySQL database. The front-end will be created with Angular 11, HttpInterceptor and Router. We’ll also perform Form validation on UI.

JWT (JSON Web Token)

Comparing with Session-based Authentication that need to store Session on Cookie, the big advantage of Token-based Authentication is that we store the JSON Web Token (JWT) on Client side: Local Storage for Browser, Keychain for IOS and SharedPreferences for Android… So we don’t need to build another backend project that supports Native Apps or an additional Authentication module for Native App users.

in-depth-introduction-jwt-token-based-authentication

There are three important parts of a JWT: Header, Payload, Signature. Together they are combined to a standard structure: header.payload.signature.

The Client typically attaches JWT in x-access-token header:

x-access-token: [header].[payload].[signature]
Enter fullscreen modeExit fullscreen mode

For more details, you can visit:
In-depth Introduction to JWT-JSON Web Token

Node.js Express Angular 11 Authentication example

It will be a full stack, with Node.js Express for back-end and Angular 11 for front-end. The access is verified by JWT Authentication.

  • User can signup new account, login with username & password.
  • Authorization by the role of the User (admin, moderator, user)

Screenshots

The images below shows screenshots of our Angular 11 Client App.

– Anyone can access a public page before logging in:

jwt-authentication-node-js-angular-11-login-registration-public-page

– A new User can signup:

jwt-authentication-node-js-angular-11-login-registration-signup-page

– Registration form validation:

jwt-authentication-node-js-angular-11-login-registration-form-validation

– Login with legal account:

jwt-authentication-node-js-angular-11-login-registration-signin-page

Profile page:

jwt-authentication-node-js-angular-11-login-registration-profile-page

– UI for admin role:

jwt-authentication-node-js-angular-11-login-registration-authorization

– If a User who doesn’t have Admin role tries to access Admin/Moderator Board page:

jwt-authentication-node-js-angular-11-login-registration-unauthorized

This is full Angular + Node.js Express JWT Authentication & Authorization App Demo (with form validation, check signup username/email duplicates, test authorization with 3 roles: Admin, Moderator, User).

In the video, we use Angular 10, but the logic and UI are the same as this Angular version 11.

Flow for User Registration and User Login

The diagram shows flow of User Registration, User Login and Authorization process.

jwt-authentication-node-js-angular-11-login-registration-flow

We have 2 endpoints for authentication:

  • api/auth/signup for User Registration
  • api/auth/signin for User Login A legal JWT must be added to HTTP x-access-token Header if Client accesses protected resources.

Back-end with Node.js Express & Sequelize

Our Node.js Express Application can be summarized in the diagram below:

jwt-authentication-node-js-angular-11-login-registration-architecture

Via Express routes, HTTP request that matches a route will be checked by CORS Middleware before coming to Security layer.

Security layer includes:

  • JWT Authentication Middleware: verify SignUp, verify token
  • Authorization Middleware: check User’s roles with record in database

If these middlewares throw any error, a message will be sent as HTTP response.

Controllers interact with MySQL Database via Sequelize and send HTTP response (token, user information, data based on roles…) to client.

Front-end with Angular 11, HttpInterceptor and Router

jwt-authentication-node-js-angular-11-login-registration-components

For more details, please visit:
https://bezkoder.com/node-js-angular-11-jwt-authentication/

Further Reading

Fullstack CRUD App:


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK