PKCE (RFC 7636)
Official docs outline
7 sections- Protocol flow
How PKCE binds the authorization code to the client.
- Code verifier
Generating a high-entropy code_verifier.
- Code challenge
Deriving code_challenge with S256 or plain.
- Authorization request
Sending code_challenge and code_challenge_method.
- Access token request
Sending code_verifier to the token endpoint.
- Server verification
How the server compares verifier and challenge.
- Security considerations
Entropy requirements, S256 vs plain and downgrade risks.
Each section links to the official page. Titles and summaries by Extra Credit; the docs belong to their authors.
More in Auth and identity
All 21- OAuth 2.0 (RFC 6749)
- OAuth 2.0 Bearer Token Usage (RFC 6750)
- OAuth 2.0 Device Authorization Grant (RFC 8628)
- OAuth 2.0 Security Best Current Practice (RFC 9700)
- OAuth 2.0 Token Exchange (RFC 8693)
- OAuth 2.1 (IETF draft)
- OpenID Connect Core 1.0
- Passkeys
- SAML 2.0
- SCIM 2.0 (RFC 7643 and 7644)
- TOTP and HOTP (RFC 6238 and 4226)
- WebAuthn (W3C Web Authentication Level 3)