Why Refresh token concept in Express? - Purpose & Use Cases

The Big Idea

What if your app could keep users logged in safely without bothering them again and again?

The Scenario

Imagine a user logs into your app and you give them a token that expires quickly for security. Now, every time the token expires, the user must log in again manually to get a new token.

The Problem

This manual re-login is annoying for users and makes your app feel broken. Also, constantly asking for passwords increases security risks and server load.

The Solution

Refresh tokens let your app silently get new access tokens without bothering the user. This keeps users logged in smoothly and securely.

Before vs After

✗ Before

if (tokenExpired) { redirectToLogin(); }

✓ After

if (tokenExpired) { useRefreshTokenToGetNewAccessToken(); }

What It Enables

It enables seamless, secure user sessions without repeated logins, improving user experience and security.

Real Life Example

Think of how apps like Gmail keep you logged in all day without asking for your password every few minutes.

Key Takeaways

Manual token expiration forces annoying re-logins.

Refresh tokens automate getting new access tokens silently.

This improves security and user experience dramatically.

Practice

1. What is the main purpose of a refresh token in an Express app using authentication?

easy

A. To encrypt the access token

B. To store user passwords securely

C. To log out the user automatically after a timeout

D. To get a new access token without asking the user to log in again

Solution

1. Step 1: Understand the role of refresh tokens

   Refresh tokens allow the app to request new access tokens without user interaction.

2. Step 2: Compare options with refresh token purpose

   Only To get a new access token without asking the user to log in again correctly describes this purpose; others describe unrelated functions.

3. Final Answer:

   To get a new access token without asking the user to log in again -> Option D

4. Quick Check:

   Refresh token purpose = get new access token without login [OK]

Hint: Refresh tokens renew access tokens silently [OK]

Common Mistakes:

• Confusing refresh token with access token
• Thinking refresh token stores passwords
• Assuming refresh token logs out users

2. Which of the following is the correct way to send a refresh token in an Express response header?

easy

A. res.setHeader('refresh-token', token);

B. res.sendRefreshToken(token);

C. res.refreshToken = token;

D. res.header('Authorization', token);

Solution

1. Step 1: Recall Express method to set headers

   Express uses res.setHeader(name, value) to set response headers.

2. Step 2: Match correct syntax for refresh token header

   res.setHeader('refresh-token', token); uses correct method and header name; others are invalid or use wrong header.

3. Final Answer:

   res.setHeader('refresh-token', token); -> Option A

4. Quick Check:

   Set header with res.setHeader(name, value) [OK]

Hint: Use res.setHeader to send custom headers [OK]

Common Mistakes:

• Using non-existent res.sendRefreshToken method
• Assigning token directly to res property
• Using wrong header like 'Authorization' for refresh token

3. Given this Express route snippet, what will be the output if the refresh token is valid?

app.post('/token', (req, res) => {
  const refreshToken = req.body.token;
  if (!refreshToken) return res.status(401).send('No token');
  if (refreshToken !== 'validtoken') return res.status(403).send('Invalid token');
  res.json({ accessToken: 'newAccessToken123' });
});

medium

A. Status 401 with message 'No token'

B. Status 403 with message 'Invalid token'

C. JSON response with new access token

D. Empty response with status 200

Solution

1. Step 1: Check token presence and validity

   If refreshToken is missing, returns 401; if invalid, returns 403.

2. Step 2: For valid token, send new access token JSON

   When token equals 'validtoken', response sends JSON with new access token.

3. Final Answer:

   JSON response with new access token -> Option C

4. Quick Check:

   Valid token returns new access token JSON [OK]

Hint: Valid token returns JSON with new access token [OK]

Common Mistakes:

• Confusing status codes for missing vs invalid token
• Expecting empty response instead of JSON
• Ignoring token validation logic

4. Identify the bug in this Express refresh token handler:

app.post('/refresh', (req, res) => {
  const token = req.body.refreshToken;
  if (!token) res.status(401).send('Missing token');
  if (token !== 'secret') res.status(403).send('Forbidden');
  res.json({ accessToken: 'newToken' });
});

medium

A. Missing return statements after res.status calls causing multiple responses

B. Incorrect property name for token in request body

C. Using res.json instead of res.send

D. No bug, code works fine

Solution

1. Step 1: Check response flow after status calls

   Without return, code continues after sending response, causing errors.

2. Step 2: Confirm need for return to stop execution

   Adding return after res.status(...).send(...) prevents multiple responses.

3. Final Answer:

   Missing return statements after res.status calls causing multiple responses -> Option A

4. Quick Check:

   Return after res.status to stop code [OK]

Hint: Always return after sending response to avoid errors [OK]

Common Mistakes:

• Not returning after res.status sends response
• Assuming res.json is wrong here
• Thinking property name is incorrect

5. You want to implement refresh token rotation in Express to improve security. Which approach correctly applies this concept?

hard

A. Keep the same refresh token forever to avoid user re-login

B. Issue a new refresh token on each use and invalidate the old one

C. Send refresh token only once during login and never again

D. Store refresh tokens in localStorage on the client side

Solution

1. Step 1: Understand refresh token rotation

   Rotation means issuing a new refresh token each time the old one is used and invalidating the old token.

2. Step 2: Evaluate options for security best practice

   Issue a new refresh token on each use and invalidate the old one matches rotation concept; others either reduce security or misuse storage.

3. Final Answer:

   Issue a new refresh token on each use and invalidate the old one -> Option B

4. Quick Check:

   Refresh token rotation = new token each use [OK]

Hint: Rotate refresh tokens by replacing old with new each use [OK]

Common Mistakes:

• Reusing same refresh token indefinitely
• Not invalidating old refresh tokens
• Storing tokens insecurely on client side