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.
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.
There are three important parts of a JWT: Header, Payload, Signature. Together they are combined to a standard structure:
The Client typically attaches JWT in x-access-token header:
For more details, you can visit:
In-depth Introduction to JWT-JSON Web Token
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)
The images below shows screenshots of our Angular 11 Client App.
– Anyone can access a public page before logging in:
– A new User can signup:
– Registration form validation:
– Login with legal account:
– Profile page:
– UI for admin role:
– If a User who doesn’t have Admin role tries to access Admin/Moderator Board page:
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.
The diagram shows flow of User Registration, User Login and Authorization process.
We have 2 endpoints for authentication:
api/auth/signupfor User Registration
api/auth/signinfor User Login A legal JWT must be added to HTTP x-access-token Header if Client accesses protected resources.
Our Node.js Express Application can be summarized in the diagram below:
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.
For more details, please visit:
- Node.js + MongoDB: JWT Authentication & Authorization
- Node.js + PostgreSQL: JWT Authentication & Authorization
Fullstack CRUD App: