Hacking OAuth
summary
Examines real breaches (Twitter API key leaks, OAuth phishing that mimicked Google Docs) and maps each to OAuth mechanics and fixes: covers authorization code with PKCE, implicit, password and client credentials, and the back-channel token exchange; documents the Security BCP recommendations to deprecate implicit and password grants, require exact redirect matching, and rotate refresh tokens (one-time use) to detect theft; describes OAuth 2.1 consolidation, dynamic client registration, and practical architectures for browser, native, and server apps.
AI-written summary · about
chapters (14)
- 0:00Introduction to OAuth
- 1:25Problem OAuth solves
- 4:55OAuth core concepts
- 7:47Front and back channel flows
- 10:53Client secrets in apps
- 13:48PKCE explained
- 18:25Implicit flow alternatives
- 20:13Password grant risks
- 25:33Redirect URL security
- 27:01OAuth 2.1 simplification
- 31:54Client types and identity
- 33:59Social engineering attacks
- 35:23OAuth 2.1 future
- 35:44Q&A session
related talks
18mHow to Hack OAuth
36mHow To Hack OAuth|
47mTop X OAuth 2 Hacks
01h 02mOpenID Connect & OAuth 2.0 – Security Best Practices
46mA Deep Dive into the Past, Present & Future of OAuth
37mHacking OAuth Pitfalls and Remedies
44mThe Art of Authentication for Web Apps
53mOpenID Connect & OAuth 2.0 – Security Best Practices
