Erik Huelsmann wrote:
>> I have a subversion server on a W2K3 machine. I have setup the
>> authentication method with SSPI so we can login to repositories with
>> our domain usernames/passwords. Everything works fine using http://
>> protocol but when we use the svn:// protocol, we can only read from
>> the repositories and can not commit. The reason is that we haven't
>> configured any svnserve.conf file. We have one repository per project
>> that results lots of repositories. I don't want to maintain
>> svnserve.conf files for each repository. Is there any way that we can
>> read from and write our repositories using svn:// protocol with SSPI
>> without dealing with .conf files?
>
> The only way to do that would be to extend svnserve yourself...
>
> bye,
>
> Erik.
You might also consider using HTTP with svnperms.conf and svnperms.py, which
can be configured to use a single svnperms.conf file and gets you finer
grained control over user access.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 17 14:58:48 2006