JSON Web Tokens
summary
Shows how JSON Web Tokens replace cookie sessions by putting header payload and signature into a compact string and signing it with a server secret so the server can verify origin and read claims. Describes the three parts and uses HMAC256 for signing, stores the token in localStorage and sends it on Authorization requests, and makes authentication stateless. Demonstrates editing the payload to show the token value changing live. Filmed at dotJS 2014 Paris.
AI-written summary · about
chapters (4)
related talks
32mPortable Sessions with JSON Web Tokens
41mJWT, WTF?
24mA Token Walks Into a SPA
28mJWT, WTF?
37mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
34mWhat makes JSON Web Tokens (JWT) secure?
54mJSON Web Tokens Suck
25mHow JSON Web Tokens Work and Can be Used to Secure Your Single Page Apps
