Authentication as a Microservice: Portable Customer Identity Management
summary
Argues for replacing session state with JSON Web Token payloads verified by RSA or HMAC, warns about the “none” and HMAC->RSA key tricks, and recommends fetching keys from a well-known JWKS endpoint and rotating by kid. Describes locking long-lived refresh tokens to device storage, using cookies or secure keychains, and a webhook-driven revocation window (example: 30 minute JWT lifetime) plus three scopes for kills: global/app/user revocation. Notes performance costs (bcrypt, RSA signing) and that these approaches scale if cached and lightweight.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 2:09How did we log into these apps
- 3:32Cookies are secure
- 4:16Why is this painful
- 5:49The evolution
- 6:44Tokenization
- 8:04Token Mapping
- 9:07JSON Web Token
- 10:01Header and Body
- 11:08Signature
- 11:21Select Change
- 11:39Show Code
- 12:26No Signature
- 13:06HMAC Hack
- 14:22RSA Public Key
- 16:17Verifying RSA Signature
- 16:36Rotating Keys
- 16:49Key ID
- 17:03JSON
- 17:15Hackproof Security
- 20:46Refresh Tokens
- 25:16Revocation
- 30:29Auth to access tokens
related talks
01h 06mMicroservice Authentication and Authorization
32mPortable Sessions with JSON Web Tokens
34mStateless Auth w/ JSON Web Tokens
39mMicroservice Security via MicroProfile JWT
37mKnock knock, who's there? Authenticating your single page apps using JSON Web Tokens
32mREST security essentials
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
