Moving application auth to the edge
summary
Claims moving application auth entirely to the edge by handling login/signup before requests reach the app and storing user state per-region. Implements a demo QR-app history feature using Cloudflare Workers and Durable Objects, performs a Discord OAuth callback, writes user records to a durable object near the user, sets an auth cookie + X-User header and proxies requests to the app. The demo builds, persists, and serves user data at low latency and the flow works end to end.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:53Why auth at edge matters
- 3:19Traditional auth challenges
- 7:12Durable objects for auth
- 8:34Architecting auth before app
- 9:59Live coding auth flow
- 12:08Implementing login and OAuth
- 15:02Handling OAuth callback
- 16:32Storing user data in durable objects
- 18:17Setting secure auth cookies
- 20:07Reading auth cookies
- 21:54Integrating auth middleware
- 23:01Demo and conclusion
related talks
09mBeyond the Login Page: Authentication in Next.js
33mFirst-Class Auth Experience In Frontend Applications
36mAdvanced Authentication patterns at the Edge
56mIP Allow lists suck Secure your staging environments with Cloudflare workers
14mLeverage Hybrid Apps for Secure Auth
39mZen and the art of edge authentication
29mYou and Your Data: A Horror Story Made Online
18mMake Auth great again with Ory