Default rights for user for new repositories

[jcdk]

Hi
We have a user, that is external to the company and will never have access to more than a few repositories. I have created him with "Default rights in source control repositories" = None, but when I create a new repository he has access to that unless I go in and actively deny him access. This is also true if I tick "Enable folder security" when I create the repository.

As we regularly create new repositories we would like to set up Vault to default assign no rights to this external user, so we would have to actively assign rights to the repositories he may access.

Any help appriciated.

Regards
Jesper Carstensen

[lbauer]

One way to do this would be to set your options so that no one has access to a repository when you first create it. This setting is in the Admin Web Client under Source Control Repositories-> Default Repository Settings ->Repository Access. Set default rights to the repository for all users to "No Access."

Then you could put all your other users in a Global group (Server Settings->Groups). In the new repository configuration, under Repository Access, you can give that global group access. This is kind of the opposite way of doing it, but right now Vault does not support denying repository access to a specific user by default.

[nairb317]

How would you do this without the web client? As the original problem stated, when we add a user, automatically that user has all current repositories checked. You then have to go in an uncheck each one. We have a large number of repositories.

In Version 3.1.9 of the Admin tool, how do you eliminate the default values so, by default, the new user has access to NO respositories?

Thanks,
Brian

[lbauer]

In Vault 4 and later, you can set repositories to have "no access" by default, then you would assign rights to each user or group as they are created.

Prior to Vault 4.0, repository access was "on" by default. You have to modify the user rights to take away access to the repository. If you're running into this issue often, I'd suggest upgrading to the latest version, Vault 5.0