Nico,
I'm sure what you meant. If you mean AuthzSVN security can only be used
for HTTP access, then that's only try for versions before 1.3.x.
Since SVN v1.3.x you can use the same authz file for HTTP and SVN
repository access. The FILE access is the only one that can't use the
authz file. This method depends on file system security.
Paul
-----Original Message-----
From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]
Sent: Tuesday, July 25, 2006 5:16 AM
To: Steve Williams; riteshn@gmail.com
Cc: users@subversion.tigris.org
Subject: Re: Project based authentication
Steve Williams wrote:
> Ritesh Nadhani wrote:
>> I would like to setup subversion in such a way like:
>>
>> -- One user has read-only access only to one particular project and
>> not anonymous which gives anon access to all the projects. He cannot
>> have read access to other projects too.
>> -- Specific write permission to particular projects. E.g. Mr. X has
>> read and write access only for project1 and project 3.
>> -- Branching can be done only by a particular person most probably
>> the project admin.
>>
>> Is this possible? If not then what would you suggest to handle such
>> situations?
>>
>
> The Subversion Book describes exactly what you need. AuthzSVN.
Unfortunately, it doesn't enforce it for other access methods. That
takes a pre-commit hook, using an approach such as svnperms.py and
svnperms.conf, which actually give better resolution of control such as
read-only, add, delete, and edit for tags and branches.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 25 15:35:06 2006