Why authorization differs from authentication in Express

Introduction

Authentication checks who you are. Authorization checks what you can do. They are different steps to keep apps safe.

When a user logs in to prove their identity.

When deciding if a user can access a page or feature.

When protecting sensitive data from unauthorized users.

When giving different permissions to different user roles.

When building secure APIs that require user validation and permission checks.

Syntax

Express

app.use(authenticate);
app.use(authorize);

Authentication usually happens before authorization.

Middleware functions in Express help separate these concerns clearly.

Examples

This middleware checks if the user sent a valid token to prove who they are.

Express

function authenticate(req, res, next) {
  // Check user identity
  if (req.headers.authorization === 'valid-token') {
    req.user = { id: 1, role: 'admin' };
    next();
  } else {
    res.status(401).send('Not authenticated');
  }
}

This middleware checks if the authenticated user has permission to access the resource.

Express

function authorize(req, res, next) {
  // Check user permission
  if (req.user.role === 'admin') {
    next();
  } else {
    res.status(403).send('Not authorized');
  }
}

Sample Program

This example shows how Express middleware first checks if the user is authenticated, then if they are authorized to access the admin page.

Express

import express from 'express';
const app = express();

function authenticate(req, res, next) {
  if (req.headers.authorization === 'valid-token') {
    req.user = { id: 1, role: 'admin' };
    next();
  } else {
    res.status(401).send('Not authenticated');
  }
}

function authorize(req, res, next) {
  if (req.user.role === 'admin') {
    next();
  } else {
    res.status(403).send('Not authorized');
  }
}

app.use(authenticate);
app.get('/admin', authorize, (req, res) => {
  res.send('Welcome Admin');
});

// Simulate a request with valid token
const req = { headers: { authorization: 'valid-token' } };
const res = {
  status(code) { this.statusCode = code; return this; },
  send(message) { this.message = message; }
};

let nextCalled = false;
function next() { nextCalled = true; }

// Run authenticate
authenticate(req, res, () => {
  // Run authorize
  authorize(req, res, () => {
    res.send('Welcome Admin');
  });
});

console.log(res.message || res.statusCode);

Important Notes

Authentication confirms identity; authorization controls access.

Always authenticate before authorizing in your app flow.

Use clear error codes: 401 for authentication failure, 403 for authorization failure.

Summary

Authentication means checking who the user is.

Authorization means checking what the user can do.

Both are important for app security but serve different purposes.

Practice

1. In Express apps, what is the main difference between authentication and authorization?

easy

A. Authentication checks what the user can access; authorization verifies who they are.

B. Authentication verifies who the user is; authorization checks what they can access.

C. Authentication and authorization both check user identity only.

D. Authorization is done before authentication in Express.

Solution

1. Step 1: Understand authentication purpose

   Authentication confirms the user's identity, like logging in.

2. Step 2: Understand authorization purpose

   Authorization decides what resources or actions the authenticated user can access.

3. Final Answer:

   Authentication verifies who the user is; authorization checks what they can access. -> Option B

4. Quick Check:

   Authentication = identity, Authorization = permissions [OK]

Hint: Authentication = who, Authorization = what they can do [OK]

Common Mistakes:

• Confusing authentication with authorization
• Thinking both check the same thing
• Assuming authorization happens before authentication

2. Which Express middleware is typically used for authentication?

easy

A. passport.authenticate()

B. cors()

C. express.json()

D. express.static()

Solution

1. Step 1: Identify authentication middleware

   Passport.js is a popular Express middleware for handling authentication.

2. Step 2: Check other options

   express.static serves files, express.json parses JSON, cors handles cross-origin requests, none handle authentication.

3. Final Answer:

   passport.authenticate() -> Option A

4. Quick Check:

   passport.authenticate() = authentication middleware [OK]

Hint: Passport is for authentication in Express [OK]

Common Mistakes:

• Choosing express.static for authentication
• Confusing cors with authentication
• Not knowing passport middleware

3. Consider this Express route snippet:

app.get('/dashboard', (req, res) => {
  if (!req.user) {
    return res.status(401).send('Not authenticated');
  }
  if (!req.user.isAdmin) {
    return res.status(403).send('Not authorized');
  }
  res.send('Welcome Admin');
});

What status code will be sent if a logged-in user is not an admin?

medium

A. 200

B. 401

C. 403

D. 500

Solution

1. Step 1: Check authentication condition

   The code checks if req.user exists; if not, sends 401 (unauthenticated).

2. Step 2: Check authorization condition

   If user exists but isAdmin is false, sends 403 (forbidden, unauthorized).

3. Final Answer:

   403 -> Option C

4. Quick Check:

   Authenticated but not authorized = 403 [OK]

Hint: 401 = no login, 403 = no permission [OK]

Common Mistakes:

• Mixing 401 and 403 status codes
• Assuming 200 is sent without admin rights
• Ignoring the authorization check

4. This Express middleware aims to protect routes:

function checkAdmin(req, res, next) {
  if (!req.user.isAdmin) {
    res.status(401).send('Unauthorized');
  }
  next();
}

What is the bug here?

medium

A. req.user might be undefined causing an error

B. Should send status 403 instead of 401 for authorization failure

C. Missing call to next() inside the if block

D. Middleware should be async

Solution

1. Step 1: Analyze req.user usage

   The code accesses req.user.isAdmin without checking if req.user exists, risking a runtime error.

2. Step 2: Check other issues

   While 403 is better for authorization failure, the main bug is possible crash from undefined req.user.

3. Final Answer:

   req.user might be undefined causing an error -> Option A

4. Quick Check:

   Always check req.user exists before properties [OK]

Hint: Check req.user exists before isAdmin [OK]

Common Mistakes:

• Ignoring possible undefined req.user
• Confusing 401 and 403 status codes
• Not returning after sending response

5. You want to protect an Express route so only authenticated users with role 'editor' or 'admin' can access it. Which middleware logic correctly implements this authorization check?

hard

A. if (req.user && req.user.role === 'admin') { next(); } else { res.status(403).send('Forbidden'); }

B. if (!req.user && (req.user.role === 'editor' || req.user.role === 'admin')) { next(); } else { res.status(401).send('Unauthorized'); }

C. if (req.user.role === 'editor' || req.user.role === 'admin') { next(); } else { res.status(401).send('Unauthorized'); }

D. if (!req.user || (req.user.role !== 'editor' && req.user.role !== 'admin')) { res.status(403).send('Forbidden'); } else { next(); }

Solution

1. Step 1: Check authentication and authorization together

   The middleware must first confirm req.user exists (authenticated), then check if role is 'editor' or 'admin'.

2. Step 2: Analyze each option

   if (!req.user || (req.user.role !== 'editor' && req.user.role !== 'admin')) { res.status(403).send('Forbidden'); } else { next(); } correctly denies access if no user or role not allowed, sending 403 Forbidden. Others have logic errors or wrong status codes.

3. Final Answer:

   if (!req.user || (req.user.role !== 'editor' && req.user.role !== 'admin')) { res.status(403).send('Forbidden'); } else { next(); } -> Option D

4. Quick Check:

   Check user exists AND role allowed for authorization [OK]

Hint: Check user exists AND role matches before next() [OK]

Common Mistakes:

• Not checking if user is authenticated first
• Using wrong status codes (401 vs 403)
• Incorrect logical operators in role check