Identity Proofing

Identity Proofing Overview

Identity Proofing lets you structure authentication work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep identity proofing focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import express from 'express';
import jwt from 'jsonwebtoken';

const app = express();
app.use(express.json());

function authenticate(req, res, next) {
  const token = req.headers.authorization?.replace('Bearer ', '');
  try {
    req.user = jwt.verify(token, process.env.JWT_SECRET);
    next();
  } catch {
    res.status(401).json({ error: 'Unauthorized' });
  }
}

Authentication middleware verifies the caller's identity before protected handlers run.

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

Authentication Cheatsheet

Quick authentication reference related to identity proofing.

How Identity Proofing Works

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

Authentication middleware verifies the caller's identity before protected handlers run.

• 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 Identity Proofing

Security is the whole point of identity proofing. 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 identity proofing.
• Leaving identity proofing untested, so regressions slip into production.
• Over-engineering identity proofing before you actually need the extra flexibility.
• Ignoring documentation, which makes identity proofing hard for the next developer to change.

Key Takeaways

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