Setting up SVN server for multiple users over http
The SVN annotate attribute is fairly effective and also makes fast job of that to locate for a certain attribute on a certain line of code. This attribute is provided a little extra minimal (yet still valuable) if customers accessibility SVN using http. There are no qualifications traded in this manner so the note reveals no name for a line changed by by a programmer that makes use of http to devote an adjustment.
The inquiry is, exists a means for a programmer to pass qualifications of some type to SVN on the web server to distinctly recognize their devote? It is just the visibility of an ID that is called for in this setting. Alternative approaches such as svn+ssh and also submit methods are not readily available. Ultimately, this web server gets on an inner LAN, not public. Tips for https additionally invite.
The SVN web server is working on Linux with Apache2.
This solution thinks your programmers make use of Windows and also your have a Active Directory domain name controller.
You can sign up with the Linux svn web server to the domain name by following this article.
From there, you set up apache to confirm to the advertisement making use of Kerberos. First install mod_auth_kerb, after that connect apache2 to kerberos for verification. See Microsoft is documenation. See to it you implement SSL if you go to all bothered with the security in between the customer and also the web server.
After you are done, customer is can visit with their Windows passwords and also tasks will certainly be appointed to their customer.
However, I can not get you details arrangement information now as I run out the workplace and also do not have accessibility to our svn web server.
You can have a little concerning apache+svn+mod_autz_svn and also something extra in my slides offered to the International PHP Conference '09 readily available at http://superalbert.it/download/misc/PHPCon09_SVN_advanced.pdf
in apache config:
<Location /svn> DAV svn SVNPath /mnt/big/svn AuthType Basic AuthName "SVN Server" AuthUserFile /etc/apache2/svn.pass Require valid-user AuthzSVNAccessFile /etc/apache2/svn_authz
and also/ etc/apache2/svn _ authz can have great - graned monitoring of that can access what:
[groups] ops=user1,user2 it=user2,user3 [/] * = rw [/ops] * = @ops=rw [/ro] * = @ops = r @it = r user4 = rw
if you have ldap / energetic directory site web server handy you can utilize it as opposed to AuthUserFile for apache verification.
Since you are running SVN via Apache, you can capitalize on Apache is constructed - in verification approaches to regulate accessibility / track adjustments to your database. The example below will certainly collaborate with an htaccess - design arrangement:
AuthType Basic AuthName "Subversion Repository" AuthUserFile /path/to/user/list Require valid-user
You can configure this in an htaccess documents, or in the VirtualHost arrangement documents.