OAuth2 & JWT Security Cheatsheet
OAuth 2.0 is an authorization framework that enables third-party applications to obtain limited access to an HTTP service. JSON Web Token (JWT) is a compact, URL-safe means of representing claims between two parties.
1. OAuth2 Grant Flows
sequenceDiagram
autonumber
actor User as User Browser
participant Client as SPA / App
participant AuthServer as Authorization Server
participant API as Resource Server
User->>Client: Click Login
Client->>AuthServer: Redirect with PKCE Code Challenge
AuthServer->>User: Display Consent Screen
User->>AuthServer: Grant Approval
AuthServer->>Client: Redirect with Auth Code
Client->>AuthServer: Exchange Auth Code + Code Verifier
AuthServer-->>Client: ID Token + Access Token (JWT) + Refresh Token
Client->>API: Bearer Authorization Request
API-->>Client: Protected Resource Data
2. JWT Anatomy
A JWT consists of three parts separated by dots (.): Header.Payload.Signature
- Header: Algorithm & token type (
{"alg": "RS256", "typ": "JWT"}) - Payload: Standard claims (
sub,iss,exp,iat,aud, custom roles) - Signature: Hash calculated with private key or secret.
Best Practices & Security Guidelines
- Use PKCE for Public Clients: Always use Proof Key for Code Exchange (PKCE) for SPAs and Mobile Apps.
- Short Token Lifetimes: Keep access tokens short-lived (e.g., 15 minutes) and refresh tokens strictly bound to secure HTTP-only cookies.
- Use Asymmetric Signing: Sign tokens using RS256/ES256 (Public/Private key pair) so Resource Servers can verify signatures without knowing the private key.