Common mistakes and misconceptions in Web App Security using OAuth 2.0 and OpenId Connect
summary
Covers concrete pitfalls: authorization code interception and injection attacks and why PKCE is required for public and recommended for confidential clients; avoid implicit and password grants, use client_credentials for server-to-server; prefer IdentityServer4 for demos and implementations; use JWT access tokens with short lifetimes and consider refresh-token rotation to allow revocation; enforce exact redirect_uri matching, HTTPS everywhere, and treat scopes as hints—APIs must combine scopes with user privileges before granting permission.
AI-written summary · about
chapters (23)
- 0:00Intro
- 2:05Authentication and Authorization
- 3:02OAuth and OpenId Connect
- 7:52Terminology
- 10:37Client Type
- 12:15Public Client
- 13:58Scopes
- 17:36Access Tokens
- 18:45JSON Web Token
- 22:48OAuth endpoints
- 26:12OAuth grant types
- 28:09OAuth grant best practices
- 34:12Authorization code injection
- 36:06Pixi
- 40:17URI
- 41:13HTTP Header
- 43:01Reference Token
- 44:05Refresh Token
- 46:58OpenId Connect
- 48:30OAuth Scopes
- 51:10OAuth Connect Endpoints
- 52:37OAuth Connect Hybrid
- 55:21Use Cases
related talks
01h 02mOpenID Connect & OAuth 2.0 – Security Best Practices
53mOpenID Connect & OAuth 2.0 – Security Best Practices
59mOpenID Connect & OAuth 2.0 – Security Best Practices
39mSecuring your apps with OAuth2 and OpenID Connect
01h 02mBuilding Clients for OpenID Connect/OAuth 2-based Systems
01h 00mImplementing OpenID Connect and OAuth 2.0 – Tips from the Trenches
45mMastering OAuth 2.0 and OpenID Connect
01h 00mOAuth – the good Parts
