How JSON Web Tokens Work and Can be Used to Secure Your Single Page Apps
summary
Explains how JWTs pack claims, expiry and audience into a base64 JSON trio and how a signature prevents tampering, showing header.payload.signature structure, common claims (iss, sub, aud, exp) and symmetric vs asymmetric signing with JWKS discovery. Recommends OAuth2 + OpenID Connect flows, warns that implicit flow is deprecated and that single‑page apps should prefer authorization code + PKCE while avoiding refresh tokens unless rotating/ sender‑constrained and don't store sensitive data in tokens.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:00Traditional Authentication
- 4:00Initial Authentication
- 8:00JSON Web Tokens
- 12:20Examples
- 14:40Comparison
- 18:40Tokenbased Authentication
related talks
34mAuthenticating your single page apps using JSON Web Tokens
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
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
37mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
26mSecuring Single Page Applications with Token Based Authentication
34mWhat makes JSON Web Tokens (JWT) secure?
