4 ms·
Is providing helpers for authentication and authorization (for example like ASP.NET MVC attributes) anywhere on the roadmap? It would be helpful not to reimple
by polskibus 12y ago
Is providing helpers for authentication and authorization (for example like ASP.NET MVC attributes) anywhere on the roadmap?
It would be helpful not to reimplement authentication routines from scratch in every project.
- chrismccord 12y agoThere are no plans to provide authentication, but since the Phoenix Router and Controllers are just Plugs, we should se e the community produce a handful of first-class auth solutions as things mature. I don't think a generic auth solution that works for everyone is easily done and would prefer third-party packages. The nice thing about Plug is these solutions should be relatively easy to add to yours stack.
- Ixiaus 12y agoWhat Python's Pyramid web-framework did well in that area was to provide the scaffolding around Access Control Lists in the application. You figured out authentication and provided a really simple function and DB table for resolving roles and permissions and the app did the rest. I think most frameworks should follow that model: provide a flexible ACL system but let the developer figure out auth.
- chrismccord 12y agoInteresting. I'll take a look at the ACL system. We're planning a Resource protocol and something along those lines could integrate nicely.
- Ixiaus 12y agoIt worked particularly well for Pyramid with it's resource hierarchy object-model. The ACL would cascade down the tree and as it was traversed it could pattern match the permissions against the tree-node acl. I actually think the model it's better suited to a functional language. I'm working on a similar extension to the Haskell snap framework.