Authentication & Authorization Architecture in the MEAN Stack
summary
Argues that authentication uses Passport/third‑party providers but real security puts authorization on the server while mirroring decisions to the client for UX, a good-cop/bad-cop split. Recommends a single enforcement bottleneck (map HTTP endpoints to Mongo handlers) and returning an authorization envelope with per‑resource canEdit flags so Angular templates hide controls but the Node server still rejects bad requests. Demonstrates a reusable Coast module applied in one project about to launch.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:24Why Authentication
- 2:42Authentication History
- 14:23Local vs Social Authentication
- 16:43Authentication Authorization
- 19:41Bottleneck
- 22:23Our Use
- 24:09Activity Based Authentication
- 28:16Filtering Method
- 29:58Application
related talks
19mAngular's User Authentication Tool Belt
26mThe Science of Authenticating Angular Apps
33mFirst-Class Auth Experience In Frontend Applications
56mImplementing authorization in web applications and APIs
54mAuthorization for modern Applications
58mImplementing authorization in web applications and APIs
39mLogin and Access Control in Angular
43mBuilding Authorization with Node.js: Dos and Don’ts