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.
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]
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:
– 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:
Demo
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.
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.
Back-end with Node.js Express & Sequelize
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.
Front-end with Angular 11, HttpInterceptor and Router
For more details, please visit:
https://bezkoder.com/node-js-angular-11-jwt-authentication/
Further Reading
- Node.js + MongoDB: JWT Authentication & Authorization
- Node.js + PostgreSQL: JWT Authentication & Authorization
Fullstack CRUD App:
- Angular + Node.js Express + MySQL example
- Angular + Node.js Express + PostgreSQL example
- Angular + Node.js Express + MongoDB example
Using HttpOnly Cookies for JWT: (updated)
Node Express + Angular: Authentication & Authorization example
Top comments (12)
This is dangerous. The JWT should not be available to the client side code at all, let alone stored in SessionStorage.
The proper way is to set the JWT as a secure, http-only cookie that isn't accessible to the client code. It removes the need for the token storage service and interceptor, because the cookie is sent automatically, and it removes the chance of the token being stolen and someone impersonating your users.
Apart from XSS attacks, which are less likely to happen IMO if you're careful with the libraries you're using, what would be other downsides to storing the token in LocalStorage?
Also, if you go with the cookie approach, you'll have to make sure that you prevent CSRF attacks from happening.
See my comment, for example session impersonation etc.
This is another example of a tutorial where it is fine for learning though not for learning how to do auth in production.
Please do not roll you're own auth in production. If you want to prototype something quickly then sure, roll your own auth, otherwise you should be using the defacto auth standard OpenID. Do not implement OpenID yourself there are a ton of providers and several good open source servers.
Do auth right, for your users sake.
Hi all, I've updated the project with HttpOnly Cookies for storing JWT:
Node Express + Angular: Authentication & Authorization example
Session impersonation, for example. In JWT approach, token is basically your session and can be used until expired. If you make it available to sites code, it becomes a target of any malicious script, browser extension etc. And if developer sets long expiration date, it becomes basically open door to your account if anyone intercepts it.
Where would that
malicious scriptcome from, assuming that the dev has done some research on the libs he/she is using and also that a modern framework is used. I'd say the same caution should be taken in the case of browsers extensions.The second problem can be mitigated by setting a short expiring date and adding a refresh token, which should last longer.
Supply chain attacks are getting more and more popular. It is not only about your project dependencies, their dependencies dependencies and so on. Even popular libraries can (and are) compromised.
Anyway, among security professionals there is a strong movement to restrict JWT to authentication and not as session tokens.
You may want to look at curity.io/resources/architect/api-... or other articles about JWT (in)security.
Makes sense. Thank you for sharing!
Man, I just came across your React Authentication articles and that reminded me of a project I was working on 2 years, where your tutorials helped me to implement user authentication properly in React and Node.js. As authentication evolves: have you ever worked with passkeys / WebAuthn. If yes, how do you see it compared to password-based authentication?
How can I test this code?
Well put together piece.
Solid pro & con talk in the comments.