Standards-based authentication for JavaScript sites
summary
Explains that browser apps must stop returning tokens in URLs and instead use the PKCE code flow; shows how an ID token (a signed JWT) and access tokens are issued, validated, and used to call APIs; demonstrates silent renew via an authorization-server session cookie and iframe and how the Auth0 SDK automates the steps; states 2019 best-current-practices reduce the attack surface and recommends greenfield adoption while advising pragmatic migration for existing apps.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:32Terminology
- 4:25OAuth history lesson
- 7:08OAuth 20 delegated authorization
- 13:25JSON Web Token
- 17:28Recap
- 18:23JavaScript Authentication
- 20:19Browser Tokens
related talks
59mSecuring Web APIs from JavaScript/SPA Applications
22mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
44mThe Art of Authentication for Web Apps
29mKnock knock, who's there? Authenticating your single page apps using JSON Web Token
40mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
01h 02mModern Authentication
01h 01mBuilding Clients for OpenID Connect/OAuth 2-based Systems
55mBuilding Perfect Authentication in Your JS Application
