Session-based vs token-based auth in Node.js - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a session in Express using the express-session middleware.

Node.js

app.use(session({ secret: '[1]', resave: false, saveUninitialized: true }));

Drag options to blanks, or click blank then click option'

A'authToken'

B'token123'

C'mySecretKey'

D'sessionToken'

Attempts:

3 left

💡 Hint

Common Mistakes

Using token-like strings instead of a secret key.

Leaving the secret empty or undefined.

The secret option in express-session is a string used to sign the session ID cookie. It should be a secret key like 'mySecretKey'.

2fill in blank

medium

Complete the code to send a JWT token after user login.

Node.js

const token = jwt.[1]({ id: user.id }, 'secretKey', { expiresIn: '1h' });

Drag options to blanks, or click blank then click option'

Averify

Bsign

Cdecode

Dencrypt

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'verify' instead of 'sign' to create a token.

Using 'decode' which only reads tokens.

The sign method creates a new JWT token with the given payload and secret.

3fill in blank

hard

Fix the error in the middleware that checks for a JWT token in the Authorization header.

Node.js

const token = req.headers.authorization?.split(' ')[[1]];

Drag options to blanks, or click blank then click option'

A1

B-1

C2

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using index 0 which is the word 'Bearer'.

Using index 2 which is out of range.

The Authorization header usually has the format 'Bearer token', so splitting by space gives ['Bearer', 'token']. The token is at index 1.

4fill in blank

hard

Fill both blanks to create a middleware that destroys the session and clears the cookie on logout.

Node.js

req.session.[1](() => { res.[2]('sessionCookie'); res.send('Logged out'); });

Drag options to blanks, or click blank then click option'

Adestroy

BclearCookie

Cend

DremoveCookie

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'end' instead of 'destroy' for sessions.

Using 'removeCookie' which is not a valid Express method.

The destroy method removes the session from the store. clearCookie removes the cookie from the browser.

5fill in blank

hard

Fill all three blanks to create a token-based auth middleware that verifies the JWT token and attaches user info to the request.

Node.js

const token = req.headers.authorization?.split(' ')[[1]];
try {
  const decoded = jwt.[2](token, '[3]');
  req.user = decoded;
  next();
} catch (err) {
  res.status(401).send('Unauthorized');
}

Drag options to blanks, or click blank then click option'

A0

B1

Cverify

DsecretKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using index 0 which is 'Bearer' instead of the token.

Using 'sign' instead of 'verify' to check the token.

Using wrong or missing secret key.

The token is at index 1 after splitting the Authorization header. The verify method checks the token with the secret key 'secretKey'.

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