A Token Walks Into a SPA...
summary
Compares a driver’s license to a JWT and shows a concrete SPA flow: authentication server issues an access token, the SPA stores token in memory and sends it with Axios as a Bearer header to API endpoints guarded by an Express check JWT middleware. Recommends not using localStorage/cookies for tokens, uses a secure session cookie on the auth domain plus silent auth via iframe to renew short-lived RS256-signed tokens. Notes token size (~300+ bytes) and suggests a server-side blacklist for revocation.
AI-written summary · about
chapters (11)
- 0:00Introduction to SPA security
- 2:25Traditional vs modern app security
- 6:42JSON web tokens explained
- 8:08Real-world token analogy
- 17:40Token auth in SPAs
- 22:34OAuth2 flow with SPAs
- 25:46Storing tokens securely
- 27:13Silent authentication
- 28:39Additional JWT resources
- 30:09Security considerations
- 31:14Summary and closing
related talks
24mA Token Walks Into a SPA
28mA Token Walks Into a SPA...
40mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
34mAuthenticating your single page apps using JSON Web Tokens
26mSecuring Single Page Applications with Token Based Authentication
37mKnock 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
27mCookies versus tokens: a paradoxical choice
