-
Notifications
You must be signed in to change notification settings - Fork 881
Roles as a Resource support for RBAC #726
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
Comments
@tjcran I see you removed the missing-details on this one. I re-added it because the existing details are pretty thin including definition of done and technical details. I am sure I have done this to you elsewhere too. |
@Emyrk is there a bit more detail you can add to the implementation? I see you added some detail. It's probably enough that you know what needs to be done but I think the idea is that anyone else would be able to pick this up and complete the work. |
Hey team! Please add your planning poker estimate with ZenHub @Emyrk @f0ssel @johnstcn |
@Emyrk is this still applicable? |
@f0ssel it is if we add more roles. Essentially right now there is an If we want to say, role |
Implement which roles can grant/delete which roles from other users. The desired method of doing this is to make each role (
member
,admin
, etc) a specific resource. Then assign permissions to create/delete the role from a user. This would allow role assignments to be enforced from the rbacAuthorize
function.As a stop gap, just have a hard coded list that on
admin
role can grant/delete roles.The text was updated successfully, but these errors were encountered: