-
Notifications
You must be signed in to change notification settings - Fork 725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Role Based Permissions #875
Comments
There was a proposal done on the demo quite a while ago: marmelab/ng-admin-demo#8 My opinion is that it's outside of ng-admin's scope to deal with roles and permissions. It shouldn't be too hard to plug your own logic in, though. |
@thehereward . Did you ever get this sorted? What did you end up doing? I'm working out the same issues right now. |
We ended up loading the currently logged in user as a constant before bootstrapping the application. After a successful login/logout we then restarted the entire application, so running the bootstrap again with an entirely new user. This isn't particularly pleasing but it does work. A (stripped down and anonymised) version of our bootstrap:
|
this works in principle but first gives error like |
We are using ng-admin in a situation where different admins are only allowed to administer different entities. For example some admins can only administer teapots whilst other admins can only administer toasters. (A third type of super admin can administer both teapots and toasters and set the roles of other admins.)
We already have out application set up with authentication. Authorization is looking a little more challenging. I suspect we have two options:
I suspect we will be going for option 2 but I thought I would raise this in case:
Thanks 😄
The text was updated successfully, but these errors were encountered: