Why Do We Really Need OAuth Anyway?
summary
OAuth exists to give apps limited tokens instead of passwords so third parties get only the data they need and access can expire. It pairs with non‑phishable MFA like WebAuthn/FIDO (USB keys, Touch ID, Face ID) by tying credentials to domains, and it centralises login for many domains via services such as accounts.google.com. OpenID Connect adds user identity on top of OAuth, and using OAuth avoids building sign‑up, recovery and password‑reset flows.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:15LIMIT/DELEGATE ACCESS TO DATA
- 12:11WHAT ABOUT FIRST-PARTY APPS?
- 22:40REGISTRATION AND ACCOUNT RECOVERY
- 27:50OAUTH PROVIDES ACCESS TO DATA
- 30:23THE FUTURE?
- 30:37HIGH SECURITY OAUTH
- 30:49OAUTH FOR HEALTH AND FINANCE
related talks
54mOAuth – the good Parts
58mOAuth – the good Parts
29mFireside Chat About OAuth 2.0
58mOAUTH, OPENID CONNECT & .NET – THE GOOD PARTS
19mOAuth and OpenID Connect in Plain English
27mIntegrating API Security Into A Comprehensive Identity Platform
01h 00mOAuth – the good Parts
31mOAuth 2.1 And OpenID Connect
