I've used mod_dav_svn for subversion access over http or https and then setup apache so it will authenticate users against active directory. Then you can control access by simply letting IT update their AD servers. For example, make sure they are in a certain group to be allowed access to certain repositories. Or, if someone quits, simply removing them from AD removes their access.
Besides just being able to move your authentication into a centralized location, sometimes you may want someone to have subversion access, but not ssh access to a machine. If you don't need centralized authentication, you could simply use svnserv with the password files or apache with htaccess files to give subversion access to users without giving them a login on the machine. It depends on your setup. If its just a few users that already have ssh access to the machines, then using svn over ssh is an easy way to do it, its encrypted over the internet, and pretty reliable. On Sep 22, 10:00 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I access subversion repositories via SSH with my trusty DSA key. Since > Net:SSH added agent forwarding I've been able to deploy without > entering any passwords for subversion. > > Can anyone describe a situation where you *wouldn't* want to use SSH > with keys for SVN access to your repositories? Are there any benefits > I'm missing? > > - Mike --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
