Possession Factors

Possession Factors Overview

Possession Factors 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 possession factors 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.

Possession Factors 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 Possession Factors example and grow it only as needed.
• Keep configuration explicit so Possession Factors behaves the same in every environment.
• Name things clearly so teammates understand your Possession Factors at a glance.
• Add tests around Possession Factors early to lock in expected behaviour.

Authentication Cheatsheet

Quick authentication reference related to possession factors.

How Possession Factors Works

Possession Factors is part of proving who a user is and what they are allowed to do. Authentication verifies identity, while authorization decides access — and possession factors 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 Possession Factors

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

Common Mistakes

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

Key Takeaways

• Possession Factors is a core part of working effectively with authentication.
• Start small and keep possession factors focused on a single responsibility.
• Apply consistent patterns so possession factors scales across your project.
• Test and document possession factors to keep it maintainable over time.