Skip to content

Email Magic Links

In this lesson you will learn email magic links in authentication, why it matters within passwordless authentication, and how to use it correctly with clear, copy-ready examples.

Email Magic Links Overview

Email Magic Links 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 email magic links focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import { generateAuthenticationOptions, verifyAuthenticationResponse }
  from '@simplewebauthn/server';

const options = await generateAuthenticationOptions({ rpID: 'example.com' });
// browser calls navigator.credentials.get(...)
const verification = await verifyAuthenticationResponse({
  response, expectedChallenge, expectedRPID: 'example.com', authenticator,
});

WebAuthn and passkeys replace passwords with device-bound public-key credentials.

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

Authentication Cheatsheet

Quick authentication reference related to email magic links.

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 Email Magic Links Works

Email Magic Links is part of proving who a user is and what they are allowed to do. Authentication verifies identity, while authorization decides access — and email magic links plays a specific role in that flow.

WebAuthn and passkeys replace passwords with device-bound public-key credentials.

  • 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 Email Magic Links

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

Key Takeaways

  • Email Magic Links is a core part of working effectively with authentication.
  • Start small and keep email magic links focused on a single responsibility.
  • Apply consistent patterns so email magic links scales across your project.
  • Test and document email magic links to keep it maintainable over time.

Pro Tip

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