First-Class Auth Experience In Frontend Applications
summary
Argues that auth belongs in the frontend as a first-class concern and demos a working stack: Permit (no-code authz), a FaaS proxy that injects secrets and lets the frontend call Stripe/AWS safely, and OPAL for realtime policy updates. Shows policy-as-code vs low/no-code, feature-toggled UI driven by permissions, and a frontend enforcement flow using JWT identity checks. Claims a usable free tier (up to 1,000 MAUs) and live demos show the approach functioning end-to-end.
AI-written summary · about
chapters (11)
- 0:00Introduction and web history
- 1:11Managing access over time
- 4:03Introduction to permit.io
- 6:15Challenges in permissions
- 8:02Engineering authorization
- 10:26Policy as code and low-code
- 12:27Implementing authorization
- 15:30Frontend-only authorization
- 18:39Feature toggling
- 22:10Summary and best practices
- 24:40Q&A session
related talks
32mAuthz as a Dev Workflow: Architecting Better Cloud Native Apps
29mAuthz as a dev workflow
43mApplication Code of Conduct - Full-Stack Policy as Code
09mBeyond the Login Page: Authentication in Next.js
54mAuthorization for modern Applications
39mAuthentication & Authorization Architecture in the MEAN Stack
45mThe Future of Authorization in Applications
18mMake Auth great again with Ory