search

reporangler / auth-service

A webservice to handle authentication for repository access
MIT License
0 stars 0 forks source link

Package Groups need a manager user #10

Closed christhomas closed 5 years ago

christhomas commented 5 years ago

Each package group could require somebody to manage it. Say the head of a department who wants to control access to who gets access to certain packages. Or remove access to some people who should not be able to access them.

So each package group should be able to nominate a user to be the manager. This user performs any action that requires the package group manager to perform an action (accept a request to join it for example)

christhomas commented 5 years ago

Probably this can be accomplished by adding permissions to users giving them different rights. I have another task which is related to this already in the list.

The first user added to a group should automatically be the manager of that group.

Related to: #14

christhomas commented 5 years ago

A user can be given PACKAGE_GROUP_ADMIN:groupname, in order to become the user responsible for any requests of this type.

However, the code which performs the requests/accept/reject lifecycle for joining a "protected group" is not yet implemented. So I'll leave this ticket open in order to document this work

christhomas commented 5 years ago

For this to be possible, it would be required to give a capability to a package group, which is not a user, therefore the current capability system is not going to work because it's relying on the user id.

I think that the user_id should also be a constraint, held inside the constraint field in order that we can do constraints of different types.

christhomas commented 5 years ago

I'll split the 'protected group' issue into a separate ticket, cause it's not the same as this problem