You would find this page useful too if you are allowing access via svnserve. You can also create groups for users and assign access rules for groups that would apply to all users in that group, the exact syntax for the same is available on the above referenced url together with some other handy options for specifying access rules. ‘:/’ means the rule is for the root of that repo, you can also control access to particular paths inside a directory. Here I have given the admin user and myself read/write access to all repos.Īll sections below control access to a particular repo whose name is inside the brackets. I was decently sure this was the right place for configuring repository based access, but did not quite had a clear idea of the syntax to be used for specifying access rules.īasic googling and this page in CollabNet’s Subversion Community book helped and I was able to quickly muster-up the following access rules that worked exactly how I wanted them to:Ī detailed explanation of the syntax is available here:īasically the section starting with controls access to all repositories. The next place I looked out was the “Access Rules” section under “Repositories” tab when logged in as admin to CollabNet Subversion Edge GUI. If the repo is accessed via http/https, the settings in these configuration files would be ignored. But comments on top of those files (specifically nf) made it very clear that these files are only used when accessing via svnserve. My imagination was I should be able to control the same via nf/authz/passwd configuration files specific to each repository. Please note that under default settings, all authenticated users have read/write access for all repositories on a CollabNet svn server. And I did not want that person to be able to access all other repos (internal to my organization) on the same svn server. It has been only recently that a need arose to restrict access to repositories for my colleagues.īasically I needed to enable access for a particular repository to a person outside my organization. And I use CollabNet’s Subversion server for all in-house SVN repos. I have been using Subversion for version control for a good time now.
0 kommentar(er)
