4 ms·
This really doesn't satisfy real world usage. Let's say I'm on github and I have a number of repositories. I want admin access over my area, the power to creat
by eterm 11y ago
This really doesn't satisfy real world usage.
Let's say I'm on github and I have a number of repositories. I want admin access over my area, the power to create and delete repositories. I do not want other people to be able to create and delete repositories.
And then I lastly want to be able to have access control over some repositories completely (private repositories).
How can you have authorisation that means that I get to sometimes create and delete repositories, that other people can have some permissions for, without having more than 2 levels of authorisation?
Just saying "groups" is just hand-waving the question away, all the complexity of role-based vs attribute based authorisation is hidden in "use groups".