Knock knock, who's there? Authenticating your single page apps using JSON Web Token
summary
Explains how JSON Web Tokens break into header/payload/signature, shows a live demo exchanging credentials for an access token and an ID token that populates a user avatar, compares opaque tokens versus JWTs, and demonstrates using the access token as a Bearer header. Recommends authorization code with PKCE instead of the implicit flow, warns do not store tokens in localStorage and avoid refresh tokens unless rotation or sender‑constraint exists, covers JWKS public-key verification and the practical pain of token invalidation.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:20Traditional Authentication
- 7:00JSON Web Token
- 11:54Access Token
- 19:41Downsides
- 21:26OAuth
- 27:01Summary
related talks
40mKnock knock, who’s there? Authenticating your single page apps using JSON Web Tokens
22mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
40mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
37mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
34mAuthenticating your single page apps using JSON Web Tokens
25mHow JSON Web Tokens Work and Can be Used to Secure Your Single Page Apps
26mSecuring Single Page Applications with Token Based Authentication
28mA Token Walks Into a SPA...
