Skip to content

Password Hashing

Password Hashing is an important part of building production-ready authentication systems. This lesson explains what password hashing means, how it works, and how to apply it with practical examples you can reuse.

Password Hashing Overview

Password Hashing 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 password hashing 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 bcrypt from 'bcryptjs';

// on registration
const hash = await bcrypt.hash(plainPassword, 12);
await db.users.create({ email, passwordHash: hash });

// on login
const user = await db.users.findByEmail(email);
const ok = await bcrypt.compare(plainPassword, user.passwordHash);
if (!ok) throw new Error('Invalid credentials');

Passwords are hashed with a slow algorithm like bcrypt and never stored in plain text.

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

Authentication Cheatsheet

Quick authentication reference related to password hashing.

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 Password Hashing Works

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

Passwords are hashed with a slow algorithm like bcrypt and never stored in plain text.

  • 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 Password Hashing

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

Key Takeaways

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

Pro Tip

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