Time-Based One-Time Passwords

Time-Based One-Time Passwords is an important part of building production-ready authentication systems. This lesson explains what time-based one-time passwords means, how it works, and how to apply it with practical examples you can reuse.

Time-Based One-Time Passwords Overview

Time-Based One-Time Passwords 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 time-based one-time passwords 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 { 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.

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

Authentication Cheatsheet

Quick authentication reference related to time-based one-time passwords.

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 Time-Based One-Time Passwords Works

Time-Based One-Time Passwords is part of proving who a user is and what they are allowed to do. Authentication verifies identity, while authorization decides access — and time-based one-time passwords 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 Time-Based One-Time Passwords

Security is the whole point of time-based one-time passwords. 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 time-based one-time passwords snippets without understanding what each line does.
Skipping error handling and edge cases when wiring up time-based one-time passwords.
Leaving time-based one-time passwords untested, so regressions slip into production.
Over-engineering time-based one-time passwords before you actually need the extra flexibility.

Key Takeaways

Time-Based One-Time Passwords is a core part of working effectively with authentication.
Start small and keep time-based one-time passwords focused on a single responsibility.
Apply consistent patterns so time-based one-time passwords scales across your project.
Test and document time-based one-time passwords to keep it maintainable over time.

Pro Tip

Pair time-based one-time passwords with automated tests from day one. It is far cheaper to catch authentication regressions in CI than in production.