I installed the SVN repository from scratch and I have successfully tagged some of my releases using the SVN copy command.
I used the SSPI auth plugin for apache, so our developers just hit the server with their network credentials, and everything works fine.
I created an AuthZ authorization file, added our developers to the groups in the file, and gave them write access to the root. I also gave anonymous users read-only root access.
Then I locked the / svn / directory with: Require-group "CORP \ CKAN0BlahBlah"
This effectively restricts new developers in the security group to read-only access until access is granted through the aAuthZ configuration file.
Now I have a few questions:
What is the correct way (other than the honor system) to prevent users from making changes to any of the "tag" directories?
Is it possible to use SSPI to traverse group members in AuthZ, instead of listing the members individually in the configuration file?
source
share