Session Fixation

Session Fixation sits at the heart of session security in authentication. This guide walks through the concept step by step, with examples, a cheatsheet, and common mistakes to avoid.

Session Fixation Overview

Session Fixation is a building block you will reach for often in authentication. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn session fixation properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real authentication projects.

import session from 'express-session';

app.use(session({
  secret: process.env.SESSION_SECRET,
  resave: false,
  saveUninitialized: false,
  cookie: { httpOnly: true, secure: true, sameSite: 'lax', maxAge: 3600000 },
}));

app.post('/login', (req, res) => {
  req.session.userId = user.id;
  res.json({ ok: true });
});

Session auth stores a server-side session and sends the user a secure, httpOnly cookie.

Session Fixation Example

// verify the caller on every protected request
function authenticate(req, res, next) {
  const token = req.headers.authorization?.replace('Bearer ', '');
  req.user = verifyToken(token); // throws if invalid
  next();
}

Start from a minimal Session Fixation example and grow it only as needed.
Keep configuration explicit so Session Fixation behaves the same in every environment.
Name things clearly so teammates understand your Session Fixation at a glance.
Add tests around Session Fixation early to lock in expected behaviour.

Authentication Cheatsheet

Quick authentication reference related to session fixation.

Concept	Example	Purpose
Hash password	`bcrypt.hash(pw, 12)`	Store credentials safely
Issue JWT	`jwt.sign(claims, secret)`	Stateless access token
Verify JWT	`jwt.verify(token, secret)`	Trust the caller
Session	`req.session.userId = id`	Server-side login state
Cookie	`httpOnly, secure, sameSite`	Protect the session token
Authorize	`requireRole('admin')`	Control what users can do
MFA	`authenticator.verify(...)`	Add a second factor

How Session Fixation Works

Session Fixation is part of proving who a user is and what they are allowed to do. Authentication verifies identity, while authorization decides access — and session fixation plays a specific role in that flow.

Session auth stores a server-side session and sends the user a secure, httpOnly cookie.

Never store or log plain-text passwords or secrets.
Prefer short-lived tokens with refresh over long-lived ones.
Always send credentials over HTTPS.
Fail closed: deny access when anything is uncertain.

Security Guidance for Session Fixation

Security is the whole point of session fixation. Small mistakes — weak hashing, tokens in localStorage, missing rate limits — are exactly what attackers look for, so follow proven defaults.

Risk	Mitigation
Credential theft	Strong hashing, MFA, HTTPS only
Token leakage	httpOnly cookies, short TTLs
Brute force	Rate limiting and lockouts
Privilege abuse	Least-privilege authorization checks

Common Mistakes

Skipping error handling and edge cases when wiring up session fixation.
Leaving session fixation untested, so regressions slip into production.
Over-engineering session fixation before you actually need the extra flexibility.
Ignoring documentation, which makes session fixation hard for the next developer to change.

Key Takeaways

Session Fixation is a core part of working effectively with authentication.
Start small and keep session fixation focused on a single responsibility.
Apply consistent patterns so session fixation scales across your project.
Test and document session fixation to keep it maintainable over time.

Pro Tip

Pair session fixation with automated tests from day one. It is far cheaper to catch authentication regressions in CI than in production.