Session-based vs token-based auth in Node.js - Quick Revision & Key Differences

Recall & Review

beginner

What is session-based authentication?

Session-based authentication stores user login info on the server. When you log in, the server creates a session and saves it. Your browser gets a session ID cookie to identify you on future requests.

beginner

How does token-based authentication work?

Token-based authentication gives you a token (like JWT) after login. You keep this token and send it with each request. The server checks the token to verify who you are, without storing session data.

intermediate

What is a key difference between session-based and token-based auth regarding server storage?

Session-based auth stores user sessions on the server, while token-based auth does not store user info on the server. Tokens carry the info themselves.

intermediate

Why might token-based authentication be better for mobile apps?

Token-based auth works well for mobile apps because tokens are easy to store and send with requests. It also works well across different domains and servers without needing shared session storage.

intermediate

What is a common security concern with token-based authentication?

Tokens can be stolen if not stored securely, leading to unauthorized access. It's important to protect tokens, use HTTPS, and set token expiration.

In session-based authentication, where is the user session stored?

A On the server

B In the user's browser local storage

C Inside the token

D On a third-party service

Session-based authentication stores user sessions on the server to track logged-in users.

What does a token usually contain in token-based authentication?

A Server session ID

B Database credentials

C Browser cookies

D User info and claims

Tokens like JWT contain user info and claims to identify the user without server storage.

Which authentication method requires the server to keep track of active sessions?

A Token-based authentication

B Session-based authentication

C Both methods

D Neither method

Session-based authentication requires the server to store session data for each logged-in user.

Why is token-based authentication often preferred for APIs?

A Because tokens are stored on the server

B Because it uses cookies automatically

C Because tokens can be sent easily with each request

D Because it requires less client-side code

Tokens are sent with each request, making token-based auth ideal for stateless APIs.

What is a common way to protect tokens from theft?

A Use HTTPS and set token expiration

B Store tokens in plain text files

C Send tokens in URL query parameters

D Share tokens publicly

Using HTTPS encrypts data in transit and token expiration limits token misuse if stolen.

Explain the main differences between session-based and token-based authentication.

Think about where user info is stored and how the server verifies identity.

Describe a scenario where token-based authentication is more suitable than session-based authentication.

Consider apps that need to work across different devices or servers.

Practice

1. Which of the following best describes session-based authentication in Node.js?

easy

A. User data is stored on the server and linked to the client via cookies.

B. User credentials are sent with every request without storing data on the server.

C. A signed token is stored on the server and sent to the client.

D. Authentication is done only once without any session or token.

Solution

1. Step 1: Understand session-based auth storage

   Session-based authentication stores user info on the server side, typically in memory or a database.

2. Step 2: Identify how client links to session

   The client receives a cookie that holds a session ID to link requests to the stored session data.

3. Final Answer:

   User data is stored on the server and linked to the client via cookies. -> Option A

4. Quick Check:

   Session-based auth = server stores data + cookie link [OK]

Hint: Session auth stores data server-side, linked by cookies [OK]

Common Mistakes:

• Thinking tokens are stored on the server in session auth
• Confusing session ID with user credentials
• Assuming session data is stored on the client

2. Which code snippet correctly sets a cookie for session-based authentication in Express.js?

easy

A. res.session('abc123');

B. res.setHeader('Authorization', 'Bearer abc123');

C. res.sendToken('abc123');

D. res.cookie('sessionId', 'abc123', { httpOnly: true });

Solution

1. Step 1: Identify Express.js method to set cookies

   Express uses res.cookie() to set cookies on the client with options like httpOnly for security.

2. Step 2: Match correct syntax for session cookie

   res.cookie('sessionId', 'abc123', { httpOnly: true }) correctly sets a cookie named 'sessionId'.

3. Final Answer:

   res.cookie('sessionId', 'abc123', { httpOnly: true }); -> Option D

4. Quick Check:

   Use res.cookie() to set session cookies [OK]

Hint: Use res.cookie() to set cookies in Express [OK]

Common Mistakes:

• Using res.setHeader for cookies instead of Authorization header
• Assuming res.sendToken is a valid Express method
• Trying to set session with res.session which doesn't exist

3. Given this token-based auth code snippet, what will be the output if the token is valid?

const jwt = require('jsonwebtoken');
const token = req.headers.authorization?.split(' ')[1];
try {
  const user = jwt.verify(token, 'secretKey');
  res.send(`User ID: ${user.id}`);
} catch {
  res.status(401).send('Unauthorized');
}

medium

A. SyntaxError

B. Unauthorized

C. User ID: [user's id from token]

D. Token string printed as is

Solution

1. Step 1: Extract token from Authorization header

   The code splits the 'Authorization' header to get the token part after 'Bearer'.

2. Step 2: Verify token and extract user info

   jwt.verify checks the token with 'secretKey' and returns the decoded user object if valid.

3. Final Answer:

   User ID: [user's id from token] -> Option C

4. Quick Check:

   Valid token returns decoded user info [OK]

Hint: Valid JWT returns decoded user info, else error [OK]

Common Mistakes:

• Assuming token is printed directly without decoding
• Confusing token verification failure with syntax error
• Ignoring optional chaining and possible undefined token

4. Identify the bug in this session-based auth middleware code snippet:

function auth(req, res, next) {
  if (!req.session.user) {
    res.status(401).send('Not logged in');
  }
  next();
}

medium

A. req.session.user should be req.user instead.

B. Missing return after sending 401 response causes next() to run anyway.

C. next() should be called before checking session.

D. res.status should be res.sendStatus.

Solution

1. Step 1: Analyze control flow after sending response

   After res.status(401).send(), the function continues and calls next(), allowing unauthorized access.

2. Step 2: Fix by adding return to stop execution

   Adding return before res.status stops the function, preventing next() from running when unauthorized.

3. Final Answer:

   Missing return after sending 401 response causes next() to run anyway. -> Option B

4. Quick Check:

   Return after response to stop middleware [OK]

Hint: Add return after res.send to prevent next() running [OK]

Common Mistakes:

• Calling next() before checking session
• Confusing req.session.user with req.user
• Using res.sendStatus instead of res.status().send()

5. You want to build a Node.js app that supports multiple devices per user and scales easily. Which authentication method is best and why?

hard

A. Token-based auth, because tokens are stateless and work well across devices.

B. Token-based auth, because it requires server to store session data.

C. Session-based auth, because cookies automatically sync across devices.

D. Session-based auth, because it stores user data on the server for security.

Solution

1. Step 1: Consider multi-device and scalability needs

   Supporting multiple devices means the server should not rely on storing session state for each device.

2. Step 2: Choose token-based auth for statelessness

   Token-based auth uses signed tokens stored client-side, allowing stateless servers and easy scaling.

3. Final Answer:

   Token-based auth, because tokens are stateless and work well across devices. -> Option A

4. Quick Check:

   Stateless tokens = scalable multi-device auth [OK]

Hint: Use token auth for scalable, multi-device apps [OK]

Common Mistakes:

• Thinking sessions sync automatically across devices
• Believing token auth requires server session storage
• Choosing session auth for scalability