In this tutorial, we’re gonna build a Node.js Express Rest API example that supports Token Based Authentication with JWT (JSONWebToken) and PostgreSQL. You’ll know:
- Appropriate Flow for User Registration & Login with JWT Authentication
- Node.js Express Architecture with CORS, Authenticaton & Authorization middlewares & Sequelize
- How to configure Express routes to work with JWT
- How to define Data Models and association for Authentication and Authorization
- Way to use Sequelize to interact with PostgreSQL Database
Related Posts:
– Node.js Express & PostgreSQL: CRUD Rest APIs example
– Node.js + MongoDB: User Authentication & Authorization with JWT
– Node.js + MySQL: User Authentication & Authorization with JWT
Fullstack (JWT Authentication & Authorization example):
– Node Express + Vue.js
– Node Express + Angular 8
– Node Express + Angular 10
– Node Express + Angular 11
– Node Express + Angular 12
– Node Express + Angular 13
– Node Express + Angular 14
– Node Express + Angular 15
– Node Express + Angular 16
– Node Express + React
Contents
- Token Based Authentication
- Overview of Node.js JWT Authentication with PostgreSQL example
- Flow for Signup & Login with JWT Authentication
- Node.js Express Architecture with Authentication & Authorization
- Technology
- Project Structure
- Create Node.js App
- Setup Express web server
- Configure PostgreSQL database & Sequelize
- Define the Sequelize Model
- Initialize Sequelize
- Configure Auth Key
- Create Middleware functions
- Create Controllers
- Define Routes
- Run & Test with Results
- Conclusion
- Source Code
- Further Reading
Token Based Authentication
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 Authorization header with Bearer prefix:
Authorization: Bearer [header].[payload].[signature]
Or only 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
Overview of Node.js Express JWT Authentication with PostgreSQL example
We will build a Node.js Express application in that:
- User can signup new account, or login with username & password.
- User information will be stored in PostgreSQL database
- By User’s role (admin, moderator, user), we authorize the User to access resources
These are APIs that we need to provide:
Methods | Urls | Actions |
---|---|---|
POST | /api/auth/signup | signup new account |
POST | /api/auth/signin | login an account |
GET | /api/test/all | retrieve public content |
GET | /api/test/user | access User’s content |
GET | /api/test/mod | access Moderator’s content |
GET | /api/test/admin | access Admin’s content |
Flow for Signup & Login with JWT Authentication
The diagram shows flow of User Registration, User Login and Authorization process.
A legal JWT must be added to HTTP x-access-token Header if Client accesses protected resources.
You will need to implement Refresh Token:
More details at: JWT Refresh Token implementation in Node.js example
Node.js Express Architecture with Authentication & Authorization
You can have an overview of our Node.js Express JWT Auth App with 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 PostgreSQL Database via Sequelize and send HTTP response (token, user information, data based on roles…) to client.
Technology
- Express 4.18.2
- bcryptjs 2.4.3
- jsonwebtoken 9.0.0
- Sequelize 6.32.1
- PostgreSQL
Project Structure
This is directory structure for our Node.js JWT Authentication with PostgreSQL application:
Let me explain it briefly.
– config
- configure PostgreSQL database & Sequelize
- configure Auth Key
– routes
- auth.routes.js: POST signup & signin
- user.routes.js: GET public & protected resources
– middlewares
- verifySignUp.js: check duplicate Username or Email
- authJwt.js: verify Token, check User roles in database
– controllers
- auth.controller.js: handle signup & signin actions
- user.controller.js: return public & protected content
– models for Sequelize Models
- user.model.js
- role.model.js
– server.js: import and initialize neccesary modules and routes, listen for connections.
Create Node.js App
First, we create a folder for our project:
$ mkdir node-js-jwt-auth-postgresql
$ cd node-js-jwt-auth-postgresql
Then we initialize the Node.js App with a package.json file:
npm init
name: (node-js-jwt-auth-postgresql)
version: (1.0.0)
description: Node.js Demo for JWT Authentication with PostgreSQL database
entry point: (index.js) server.js
test command:
git repository:
keywords: node js, express, jwt, authentication, postgresql
author: bezkoder
license: (ISC)
Is this ok? (yes) yes
We need to install necessary modules: express
, cors
, sequelize
, pg
, pg-hstore
, jsonwebtoken
and bcryptjs
.
Run the command:
npm install express sequelize pg pg-hstore cors jsonwebtoken bcryptjs --save
*pg
for PostgreSQL and pg-hstore
for converting data into the PostgreSQL hstore format.
The package.json file now looks like this:
{
"name": "node-js-jwt-auth-postgresql",
"version": "1.0.0",
"description": "Node.js Demo for JWT Authentication with PostgreSQL database",
"main": "server.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [
"node js",
"jwt",
"authentication",
"express",
"postgresql"
],
"author": "bezkoder",
"license": "ISC",
"dependencies": {
"bcryptjs": "^2.4.3",
"cors": "^2.8.5",
"express": "^4.18.2",
"jsonwebtoken": "^9.0.0",
"pg": "^8.11.1",
"pg-hstore": "^2.3.4",
"sequelize": "^6.32.1"
}
}
Setup Express web server
In the root folder, let’s create a new server.js file:
const express = require("express");
const cors = require("cors");
const app = express();
var corsOptions = {
origin: "http://localhost:8081"
};
app.use(cors(corsOptions));
// parse requests of content-type - application/json
app.use(express.json());
// parse requests of content-type - application/x-www-form-urlencoded
app.use(express.urlencoded({ extended: true }));
// simple route
app.get("/", (req, res) => {
res.json({ message: "Welcome to bezkoder application." });
});
// set port, listen for requests
const PORT = process.env.PORT || 8080;
app.listen(PORT, () => {
console.log(`Server is running on port ${PORT}.`);
});
Let me explain what we’ve just done:
– import express
and cors
modules:
- Express is for building the Rest apis
- cors provides Express middleware to enable CORS
– create an Express app, then add cors
middlewares using app.use()
method. Notice that we set origin: http://localhost:8081
.
– define a GET route which is simple for test.
– listen on port 8080 for incoming requests.
Now let’s run the app with command: node server.js
.
Open your browser with url http://localhost:8080/, you will see:
Configure PostgreSQL database & Sequelize
In the app folder, create config folder for configuration with db.config.js file like this:
module.exports = {
HOST: "localhost",
USER: "postgres",
PASSWORD: "123",
DB: "testdb",
dialect: "postgres",
pool: {
max: 5,
min: 0,
acquire: 30000,
idle: 10000
}
};
First five parameters are for PostgreSQL connection.
pool
is optional, it will be used for Sequelize connection pool configuration:
max
: maximum number of connection in poolmin
: minimum number of connection in poolidle
: maximum time, in milliseconds, that a connection can be idle before being releasedacquire
: maximum time, in milliseconds, that pool will try to get connection before throwing error
For more details, please visit API Reference for the Sequelize constructor.
Define the Sequelize Model
In models folder, create User
and Role
data model as following code:
models/user.model.js
module.exports = (sequelize, Sequelize) => {
const User = sequelize.define("users", {
username: {
type: Sequelize.STRING
},
email: {
type: Sequelize.STRING
},
password: {
type: Sequelize.STRING
}
});
return User;
};
models/role.model.js
module.exports = (sequelize, Sequelize) => {
const Role = sequelize.define("roles", {
id: {
type: Sequelize.INTEGER,
primaryKey: true
},
name: {
type: Sequelize.STRING
}
});
return Role;
};
These Sequelize Models represents users & roles table in PostgreSQL database.
After initializing Sequelize, we don’t need to write CRUD functions, Sequelize supports all of them:
- create a new User:
create(object)
- find a User by id:
findByPk(id)
- find a User by email:
findOne({ where: { email: ... } })
- get all Users:
findAll()
- find all Users by username:
findAll({ where: { username: ... } })
These functions will be used in our Controllers and Middlewares.
Initialize Sequelize
Now create app/models/index.js with content like this:
const config = require("../config/db.config.js");
const Sequelize = require("sequelize");
const sequelize = new Sequelize(
config.DB,
config.USER,
config.PASSWORD,
{
host: config.HOST,
dialect: config.dialect,
pool: {
max: config.pool.max,
min: config.pool.min,
acquire: config.pool.acquire,
idle: config.pool.idle
}
}
);
const db = {};
db.Sequelize = Sequelize;
db.sequelize = sequelize;
db.user = require("../models/user.model.js")(sequelize, Sequelize);
db.role = require("../models/role.model.js")(sequelize, Sequelize);
db.role.belongsToMany(db.user, {
through: "user_roles"
});
db.user.belongsToMany(db.role, {
through: "user_roles"
});
db.ROLES = ["user", "admin", "moderator"];
module.exports = db;
The association between Users and Roles is Many-to-Many relationship:
– One User can have several Roles.
– One Role can be taken on by many Users.
We use User.belongsToMany(Role)
to indicate that the user model can belong to many Roles and vice versa.
With through, foreignKey, otherKey
, we’re gonna have a new table user_roles as connection between users and roles table via their primary key as foreign keys.
If you want to know more details about how to make Many-to-Many Association with Sequelize and Node.js, please visit:
Sequelize Many-to-Many Association example
Don’t forget to call sync()
method in server.js.
...
const app = express();
app.use(...);
const db = require("./app/models");
const Role = db.role;
db.sequelize.sync({force: true}).then(() => {
console.log('Drop and Resync Db');
initial();
});
...
function initial() {
Role.create({
id: 1,
name: "user"
});
Role.create({
id: 2,
name: "moderator"
});
Role.create({
id: 3,
name: "admin"
});
}
initial()
function helps us to create 3 rows in database.
In development, you may need to drop existing tables and re-sync database. So you can use force: true
as code above.
For production, just insert these rows manually and use sync()
without parameters to avoid dropping data:
...
const app = express();
app.use(...);
const db = require("./app/models");
db.sequelize.sync();
...
Learn how to implement Sequelize One-to-Many Relationship at:
Sequelize Associations: One-to-Many example
Configure Auth Key
jsonwebtoken functions such as verify()
or sign()
use algorithm that needs a secret key (as String) to encode and decode token.
In the app/config folder, create auth.config.js file with following code:
module.exports = {
secret: "bezkoder-secret-key"
};
You can create your own secret
String.
Create Middleware functions
To verify a Signup action, we need 2 functions:
– check if username
or email
is duplicate or not
– check if roles
in the request is existed or not
middleware/verifySignUp.js
const db = require("../models");
const ROLES = db.ROLES;
const User = db.user;
checkDuplicateUsernameOrEmail = (req, res, next) => {
// Username
User.findOne({
where: {
username: req.body.username
}
}).then(user => {
if (user) {
res.status(400).send({
message: "Failed! Username is already in use!"
});
return;
}
// Email
User.findOne({
where: {
email: req.body.email
}
}).then(user => {
if (user) {
res.status(400).send({
message: "Failed! Email is already in use!"
});
return;
}
next();
});
});
};
checkRolesExisted = (req, res, next) => {
if (req.body.roles) {
for (let i = 0; i < req.body.roles.length; i++) {
if (!ROLES.includes(req.body.roles[i])) {
res.status(400).send({
message: "Failed! Role does not exist = " + req.body.roles[i]
});
return;
}
}
}
next();
};
const verifySignUp = {
checkDuplicateUsernameOrEmail: checkDuplicateUsernameOrEmail,
checkRolesExisted: checkRolesExisted
};
module.exports = verifySignUp;
To process Authentication & Authorization, we have these functions:
- check if token
is provided, legal or not. We get token from x-access-token of HTTP headers, then use jsonwebtoken's verify()
function.
- check if roles
of the user contains required role or not.
middleware/authJwt.js
const jwt = require("jsonwebtoken");
const config = require("../config/auth.config.js");
const db = require("../models");
const User = db.user;
verifyToken = (req, res, next) => {
let token = req.headers["x-access-token"];
if (!token) {
return res.status(403).send({
message: "No token provided!"
});
}
jwt.verify(token,
config.secret,
(err, decoded) => {
if (err) {
return res.status(401).send({
message: "Unauthorized!",
});
}
req.userId = decoded.id;
next();
});
};
isAdmin = (req, res, next) => {
User.findByPk(req.userId).then(user => {
user.getRoles().then(roles => {
for (let i = 0; i < roles.length; i++) {
if (roles[i].name === "admin") {
next();
return;
}
}
res.status(403).send({
message: "Require Admin Role!"
});
return;
});
});
};
isModerator = (req, res, next) => {
User.findByPk(req.userId).then(user => {
user.getRoles().then(roles => {
for (let i = 0; i < roles.length; i++) {
if (roles[i].name === "moderator") {
next();
return;
}
}
res.status(403).send({
message: "Require Moderator Role!"
});
});
});
};
isModeratorOrAdmin = (req, res, next) => {
User.findByPk(req.userId).then(user => {
user.getRoles().then(roles => {
for (let i = 0; i < roles.length; i++) {
if (roles[i].name === "moderator") {
next();
return;
}
if (roles[i].name === "admin") {
next();
return;
}
}
res.status(403).send({
message: "Require Moderator or Admin Role!"
});
});
});
};
const authJwt = {
verifyToken: verifyToken,
isAdmin: isAdmin,
isModerator: isModerator,
isModeratorOrAdmin: isModeratorOrAdmin
};
module.exports = authJwt;
middleware/index.js
const authJwt = require("./authJwt");
const verifySignUp = require("./verifySignUp");
module.exports = {
authJwt,
verifySignUp
};
Create Controllers
Controller for Authentication
There are 2 main functions for Authentication:
- signup
: create new User in database (role is user if not specifying role)
- signin
:
- find
username
of the request in database, if it exists - compare
password
withpassword
in database using bcrypt, if it is correct - generate a token using jsonwebtoken
- return user information & access Token
controllers/auth.controller.js
const db = require("../models");
const config = require("../config/auth.config");
const User = db.user;
const Role = db.role;
const Op = db.Sequelize.Op;
var jwt = require("jsonwebtoken");
var bcrypt = require("bcryptjs");
exports.signup = (req, res) => {
// Save User to Database
User.create({
username: req.body.username,
email: req.body.email,
password: bcrypt.hashSync(req.body.password, 8)
})
.then(user => {
if (req.body.roles) {
Role.findAll({
where: {
name: {
[Op.or]: req.body.roles
}
}
}).then(roles => {
user.setRoles(roles).then(() => {
res.send({ message: "User was registered successfully!" });
});
});
} else {
// user role = 1
user.setRoles([1]).then(() => {
res.send({ message: "User was registered successfully!" });
});
}
})
.catch(err => {
res.status(500).send({ message: err.message });
});
};
exports.signin = (req, res) => {
User.findOne({
where: {
username: req.body.username
}
})
.then(user => {
if (!user) {
return res.status(404).send({ message: "User Not found." });
}
var passwordIsValid = bcrypt.compareSync(
req.body.password,
user.password
);
if (!passwordIsValid) {
return res.status(401).send({
accessToken: null,
message: "Invalid Password!"
});
}
const token = jwt.sign({ id: user.id },
config.secret,
{
algorithm: 'HS256',
allowInsecureKeySizes: true,
expiresIn: 86400, // 24 hours
});
var authorities = [];
user.getRoles().then(roles => {
for (let i = 0; i < roles.length; i++) {
authorities.push("ROLE_" + roles[i].name.toUpperCase());
}
res.status(200).send({
id: user.id,
username: user.username,
email: user.email,
roles: authorities,
accessToken: token
});
});
})
.catch(err => {
res.status(500).send({ message: err.message });
});
};
Controller for testing Authorization
There are 4 functions:
– /api/test/all
for public access
– /api/test/user
for loggedin users (role: user/moderator/admin)
– /api/test/mod
for users having moderator role
– /api/test/admin
for users having admin role
controllers/user.controller.js
exports.allAccess = (req, res) => {
res.status(200).send("Public Content.");
};
exports.userBoard = (req, res) => {
res.status(200).send("User Content.");
};
exports.adminBoard = (req, res) => {
res.status(200).send("Admin Content.");
};
exports.moderatorBoard = (req, res) => {
res.status(200).send("Moderator Content.");
};
Now, do you have any question? Would you like to know how we can combine middlewares with controller functions?
Let's do it in the next section.
Define Routes
When a client sends request for an endpoint using HTTP request (GET, POST, PUT, DELETE), we need to determine how the server will response by setting up the routes.
We can separate our routes into 2 part: for Authentication and for Authorization (accessing protected resources).
Authentication:
- POST
/api/auth/signup
- POST
/api/auth/signin
routes/auth.routes.js
const { verifySignUp } = require("../middleware");
const controller = require("../controllers/auth.controller");
module.exports = function(app) {
app.use(function(req, res, next) {
res.header(
"Access-Control-Allow-Headers",
"x-access-token, Origin, Content-Type, Accept"
);
next();
});
app.post(
"/api/auth/signup",
[
verifySignUp.checkDuplicateUsernameOrEmail,
verifySignUp.checkRolesExisted
],
controller.signup
);
app.post("/api/auth/signin", controller.signin);
};
Authorization:
- GET
/api/test/all
- GET
/api/test/user
for loggedin users (user/moderator/admin) - GET
/api/test/mod
for moderator - GET
/api/test/admin
for admin
routes/user.routes.js
const { authJwt } = require("../middleware");
const controller = require("../controllers/user.controller");
module.exports = function(app) {
app.use(function(req, res, next) {
res.header(
"Access-Control-Allow-Headers",
"x-access-token, Origin, Content-Type, Accept"
);
next();
});
app.get("/api/test/all", controller.allAccess);
app.get(
"/api/test/user",
[authJwt.verifyToken],
controller.userBoard
);
app.get(
"/api/test/mod",
[authJwt.verifyToken, authJwt.isModerator],
controller.moderatorBoard
);
app.get(
"/api/test/admin",
[authJwt.verifyToken, authJwt.isAdmin],
controller.adminBoard
);
};
Don't forget to add these routes in server.js:
...
// routes
require('./app/routes/auth.routes')(app);
require('./app/routes/user.routes')(app);
// set port, listen for requests
...
Run & Test with Results
Run Node.js application with command: node server.js
Tables that we define in models package will be automatically generated in PostgreSQL Database.
If you check the database, you can see things like this:
testdb=# \d users
Table "public.users"
Column | Type | Modifiers
-----------+--------------------------+----------------------------------------------------
id | integer | not null default nextval('users_id_seq'::regclass)
username | character varying(255) |
email | character varying(255) |
password | character varying(255) |
createdAt | timestamp with time zone | not null
updatedAt | timestamp with time zone | not null
Indexes:
"users_pkey" PRIMARY KEY, btree (id)
Referenced by:
TABLE "user_roles" CONSTRAINT "user_roles_userId_fkey" FOREIGN KEY ("userId") REFERENCES users(id) ON UPDATE CASCADE ON DELETE CASCADE
testdb=# \d roles
Table "public.roles"
Column | Type | Modifiers
-----------+--------------------------+-----------
id | integer | not null
name | character varying(255) |
createdAt | timestamp with time zone | not null
updatedAt | timestamp with time zone | not null
Indexes:
"roles_pkey" PRIMARY KEY, btree (id)
Referenced by:
TABLE "user_roles" CONSTRAINT "user_roles_roleId_fkey" FOREIGN KEY ("roleId") REFERENCES roles(id) ON UPDATE CASCADE ON DELETE CASCADE
testdb=# \d user_roles
Table "public.user_roles"
Column | Type | Modifiers
-----------+--------------------------+-----------
createdAt | timestamp with time zone | not null
updatedAt | timestamp with time zone | not null
roleId | integer | not null
userId | integer | not null
Indexes:
"user_roles_pkey" PRIMARY KEY, btree ("roleId", "userId")
Foreign-key constraints:
"user_roles_roleId_fkey" FOREIGN KEY ("roleId") REFERENCES roles(id) ON UPDATE CASCADE ON DELETE CASCADE
"user_roles_userId_fkey" FOREIGN KEY ("userId") REFERENCES users(id) ON UPDATE CASCADE ON DELETE CASCADE
testdb=# select * from roles;
id | name | createdAt | updatedAt
----+-----------+----------------------------+----------------------------
1 | user | 2020-11-19 21:09:51.826+07 | 2020-11-19 21:09:51.826+07
2 | moderator | 2020-11-19 21:09:51.828+07 | 2020-11-19 21:09:51.828+07
3 | admin | 2020-11-19 21:09:51.828+07 | 2020-11-19 21:09:51.828+07
(3 rows)
Register some users with /signup
API:
- admin with
admin
role - mod with
moderator
anduser
roles - zkoder with
user
role
Our tables after registration could look like this.
testdb=# select * from users;
id | username | email | password | createdAt | updatedAt
----+----------+--------------------+--------------------------------------------------------------+----------------------------+----------------------------
1 | admin | [email protected] | $2a$08$T0B0i/96KE90jAYPOhpsN.vJGVPMfFw.FbxljzuQkkN4ZK3YauRLq | 2020-11-19 21:20:49.305+07 | 2020-11-19 21:20:49.305+07
2 | mod | [email protected] | $2a$08$CmCiT5Y/9OTUM0ofSP2r2eQSHVIcqhjp1wH.GYA5oPcRlJ7Hr2C66 | 2020-11-19 21:21:13.67+07 | 2020-11-19 21:21:13.67+07
3 | user | [email protected] | $2a$08$f.exOM3efA4DF4BtohzhAOzcv2.iCppJIbdSHFLRmka569sCNXfSe | 2020-11-19 21:23:00.978+07 | 2020-11-19 21:23:00.978+07
(3 rows)
testdb=# select * from user_roles;
createdAt | updatedAt | roleId | userId
----------------------------+----------------------------+--------+--------
2020-11-19 21:20:50.045+07 | 2020-11-19 21:20:50.045+07 | 3 | 1
2020-11-19 21:21:14.604+07 | 2020-11-19 21:21:14.604+07 | 1 | 2
2020-11-19 21:21:14.604+07 | 2020-11-19 21:21:14.604+07 | 2 | 2
2020-11-19 21:23:02.1+07 | 2020-11-19 21:23:02.1+07 | 1 | 3
(4 rows)
Access public resource: GET /api/test/all
Access protected resource: GET /api/test/user
Login an account (with wrong password): POST /api/auth/signin
Login a correct account: POST /api/auth/signin
Access protected resources:
- GET
/api/test/user
- GET
/api/test/mod
- GET
/api/test/admin
Conclusion
Congratulation!
Today we've learned so many interesting things about Node.js JWT (JSONWebToken) Authentication & Authorization example with PostgreSQL database.
Despite we wrote a lot of code, I hope you will understand the overall architecture of the application, and apply it in your project at ease.
You should continue to know how to implement Refresh Token:
JWT Refresh Token implementation in Node.js example
If you need a working front-end for this back-end, you can find Client App in the post:
- Vue
- Angular 8 / Angular 10 / Angular 11 / Angular 12 / Angular 13
- React / React Hooks / React + Redux
Happy learning! See you again.
Further Reading
- https://www.npmjs.com/package/express
- https://www.npmjs.com/package/pg
- http://expressjs.com/en/guide/routing.html
- In-depth Introduction to JWT-JSON Web Token
- Sequelize Associations
Fullstack CRUD Application:
- Vue.js + Node.js Express + PostgreSQL example
- Angular 8 + Node.js Express + PostgreSQL example
- Angular 10 + Node.js Express + PostgreSQL example
- Angular 11 + Node.js Express + PostgreSQL example
- Angular 12 + Node.js Express + PostgreSQL example
- Angular 13 + Node.js Express + PostgreSQL example
- Angular 14 + Node.js Express + PostgreSQL example
- Angular 15 + Node.js Express + PostgreSQL example
- Angular 16 + Node.js Express + PostgreSQL example
- React + Node.js Express + PostgreSQL example
Source Code
You can find the complete source code for this tutorial on Github.
Many thanks for the tutorial!
how can i implement google sso in this method?
Why endpoint “/api/auth/signup” has roles (admin, moderator) in JSON input? Isn’t it security issue? Otherwise, very excellent tutorial. Thank you
Hi, it is just for testing with role submission 🙂
Thank you
Would it be possible for any of you to elaborate a bit on why this might be a security issue?. Thank you in advance
How could I make this with vue.js
Hi, the vue app in following tutorials will work with this Node.js server:
– Vue 2 JWT Authentication with Vuex, Axios and Vue Router
– Vue 3 JWT Authentication with Vuex and Vue Router
Good tutorial for authentication using Node.js! How about the frontend?
Thanks for this amazing tutorial on using PostgreSQL .
It will be helpful if u have a turotial that helps us to connect the tutroial table that you created earlier into the user.controller file in which user and admin have different type of access to the tutorial Apis
Hi bezkoder, There is new users add roles in your auth.controller.js code. But i don’t understand send roles for new user register. How can i add roles to new users that roles select on the vue register UI with options? Thank you.
This Node tutorial is awesome! Really appreciate it!
This is nice article thanks for sharing with us.
Very good tutorial. Thank you bezkoder.
Unable to connect to server:
could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host “localhost” (::1) and accepting
TCP/IP connections on port 5432?
could not connect to server: Connection refused (0x0000274D/10061)
Is the server running on host “localhost” (127.0.0.1) and accepting
TCP/IP connections on port 5432?
Hey its me again, this is the error I keep getting when I’m trying to set up a server on pg admin and nothing online seem to help
Hey, how do I connect the database to Postgresql pg-admin or from my command line like I am at the step where you said to run everything and check the tables but I do not know what to do,
Hi, you can open the cmd and run the command:
psql testdb postgres
.similar problem….I don’t see any part about connecting to the postgres db.
Very helpful. Thank you!
Thank you it very help me to learn