Hi,
We have a "local" repository administrator (group right: full admin) for each repository. He would like to obliterate a file, but is unable to do so. Message saying he need admin rights. If we are using global admin account, we are able to obliterate the file. Is this a bug or is the system designed this way? We are using Vault v4.0.4.
Regards,
Kim
Obliterate question
Moderator: SourceGear
I ran a quick check and I believe I got the same results. I don't believe that is what is supposed to happen, so I will log a bug to get this in front of the developers. Good catch.
Just to make sure though, please check to see that your repository Admin can perform the other repository Admin functions and let me know the result.
Just to make sure though, please check to see that your repository Admin can perform the other repository Admin functions and let me know the result.
We found one more irregularity:
- 1) User have access rights to repository
2) Upgrade Vault server from 3.x to 4.x
3) Create new local repository group with admin rights and assign user to this group
4) User is now directly assigned with “access” rights and is also member of group with “full admin” rights
5) When user tries to login to admin tool, he does not have admin rights to repository
6) Must delete “Directly assigned” assignment to fix problem
What you are seeing is by design. How the rights are applied are in this order:
If you go to the Users page in the Admin webpage, and click Overview, you should be able to see the rights for that user. Is there more you are wishing to see there?
- 1) Default rights
2) Group rights
3) Directly assigned individual rights
If you go to the Users page in the Admin webpage, and click Overview, you should be able to see the rights for that user. Is there more you are wishing to see there?