Course contentsShow
← System Design
Lesson 914 of 1,91924. Authentication and Authorization at ScaleFree lesson

Stateless Token Verification

How servers verify JWTs without database lookups: check signature validity, expiration, and extract claims from payload.

Stateless Token Verification

What You'll Learn

You'll learn how servers verify JWTs without hitting a database, making authentication fast and scalable.

The Core Idea

When a server receives a JWT (JSON Web Token), it doesn't need to check a database to validate it—everything needed is in the token itself. This is what makes token-based authentication "stateless."

Here's the three-step verification process:

1. Signature Validity

The server uses the signing key (the same secret used when creating the JWT) to recompute the signature from the token's header and payload. If the recomputed signature matches the one attached to the token, the token hasn't been tampered with. Think of it like a wax seal on a letter—if it's broken or wrong, you know someone messed with the contents.

2. Expiration Check

The server reads the exp (expiration) claim from the payload. If the current time is past this timestamp, the token is expired and rejected—even if the signature is valid. This prevents old tokens from being reused indefinitely.

3. Extract Claims

Once verified, the server reads claims from the payload (like userId, role, or email) to identify and authorize the user. No database lookup needed—everything is right there in the token.

Why This Matters

This approach eliminates the bottleneck of session lookups. Every server instance can independently verify tokens without coordinating with a central session store. You can scale horizontally without worrying about distributed session management.

The tradeoff? You can't revoke a token before it expires (without additional infrastructure), since the server doesn't track which tokens exist.

Key Takeaway: Stateless token verification checks signature integrity and expiration locally, then extracts claims—enabling fast, scalable authentication without database dependencies.