Recovery Codes

Recovery Codes is an important part of building production-ready authentication systems. This lesson explains what recovery codes means, how it works, and how to apply it with practical examples you can reuse.

Recovery Codes Overview

Recovery Codes 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 recovery codes focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import { authenticator } from 'otplib';

// enrolment: show this secret as a QR code
const secret = authenticator.generateSecret();
const uri = authenticator.keyuri(user.email, 'MyApp', secret);

// verification at login
const isValid = authenticator.verify({ token: userCode, secret });

TOTP-based MFA generates a shared secret and verifies rotating 6-digit codes.

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

Authentication Cheatsheet

Quick authentication reference related to recovery codes.

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 Recovery Codes Works

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

TOTP-based MFA generates a shared secret and verifies rotating 6-digit codes.

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 Recovery Codes

Security is the whole point of recovery codes. 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

Copying recovery codes snippets without understanding what each line does.
Skipping error handling and edge cases when wiring up recovery codes.
Leaving recovery codes untested, so regressions slip into production.
Over-engineering recovery codes before you actually need the extra flexibility.

Key Takeaways

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

Pro Tip

When you get stuck on recovery codes, reduce it to the smallest reproducible example first — most authentication issues become obvious once the noise is gone.