Identity & Authentication 🔐

A 6-stage, 26-submodule curriculum that takes you from “what is a token?” to designing zero-trust, multi-tenant, cross-cloud identity fabrics. Built for DevOps/SRE/Security engineers who have to ship identity, not just consume it.

Curriculum Map

StageFocusModulesStatus
Stage 0Primitives — crypto, encoding, HTTP/TLS alphabet3⬜
Stage 1JWT — the token, end to end5⬜
Stage 2OAuth 2.0 — the authorization framework6⬜
Stage 3OIDC — identity layer on top of OAuth5⬜
Stage 4Federation, SSO, SAML 2.0, B2B6⬜
Stage 5Security, attacks, hardening, SIEM4⬜
Stage 6Production, scale, frontier (DPoP, PAR, FAPI)4⬜
CapstoneKeycloak reference lab + incident tabletop2⬜

Total: 26 submodules + 2 capstone deliverables.

How to Use This Curriculum

  1. Linear path — start at stage 0, do all modules in order, finish with the capstone. Designed so each module assumes the prior stages are done.
  2. Reference path — jump straight to the stage you need (e.g. an engineer debugging JWT validation goes to Stage 1.3).
  3. Code-first — every module has working Python/Go snippets you can run, plus a DevOps analogy section tying it to infrastructure you already know.

Audience

  • DevOps/SRE engineers building or operating auth services
  • Security engineers designing zero-trust architectures
  • Platform engineers integrating OIDC into internal platforms
  • Backend engineers who own the auth code and need to understand why, not just how

Prerequisites

  • Comfort with HTTP, JSON, basic Linux/CLI
  • Basic Python (all code examples are Python or Go)
  • No prior auth experience required — Stage 0 builds the alphabet

Conventions

  • Every module has the same skeleton: Concept → How it works → Code → DevOps analogy → Attacks/pitfalls → Exercises
  • Wikilinks use the canonical form [stageN/MM-slug|Display Name]
  • YAML frontmatter on every file (title, tags, date, description)
  • Code blocks are language-tagged and runnable

More in this section

  • SAML — Imagine a scenario: You need to access multiple web applications at work, each with its own login system. Logging in to each one…

Further reading

Across the wiki