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

Token-Based Authentication Fundamentals

How token-based auth works: server issues self-contained tokens, client includes token in requests, no server-side state.

Token-Based Authentication Fundamentals

What you'll learn: How token-based authentication eliminates server-side session state by issuing self-contained tokens that clients present with every request.

The Core Idea

Unlike session-based authentication where the server maintains state about logged-in users, token-based authentication makes authentication stateless. When you log in, the server creates a self-contained token—a digitally signed piece of data containing your identity and permissions. This token is sent to your client (browser, mobile app), and you include it in every subsequent request. The server verifies the token's signature without needing to look anything up in a database or session store.

How It Works

  1. Login: Client sends credentials to the server
  2. Token Issuance: Server validates credentials and generates a signed token (often a JWT—JSON Web Token)
  3. Client Storage: Client stores the token (typically in memory, localStorage, or a cookie)
  4. Authenticated Requests: Client includes the token in request headers (usually Authorization: Bearer <token>)
  5. Verification: Server validates the token's signature and extracts user information directly from the token payload

The "Boarding Pass" Analogy

Think of a token like an airline boarding pass. When you check in (authenticate), the airline issues a boarding pass with your name, flight details, and a barcode. At the gate, the agent scans it to verify its authenticity—they don't need to call headquarters to check if you're allowed on the plane. The boarding pass itself contains all necessary information and is cryptographically secure (the barcode).

Why This Matters

This approach enables horizontal scaling without sticky sessions or shared session storage. Any server can validate any token because the truth is in the token itself, not in server memory.

Key Takeaway: Token-based authentication eliminates server-side session state by issuing cryptographically signed, self-contained tokens that clients present with each request, enabling truly stateless and horizontally scalable authentication.