Knock knock, who's there? Authenticating your single page apps using JSON Web Tokens
summary
Explains exactly what a JWT contains and how to use one: the header/payload/signature structure, how signatures prevent tampering, and how to verify tokens via a jwks endpoint. Demonstrates a single‑page app + Auth0 using OpenID Connect to return ID and access tokens and shows calling an API with a Bearer token. Recommends the authorization code with PKCE flow, stores tokens in memory not localStorage, and warns that revocation still requires a blacklist or server state.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:33Traditional Authentication
- 4:45What Are some of the Problems with Traditional Cookie Based Approach
- 6:56Json Web Tokens
- 7:11Parts of Json Web Token
- 7:57Payload
- 8:51Public Claim
- 9:23Private Claims
- 9:46Signature
- 16:07Are There some Downsides to the Json Web Tokens
- 16:22Invalidation of Tokens
- 17:00Token-Based Authentication
related talks
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
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
30mStandards-based authentication for JavaScript sites
