Re: Project based authentication

[Steve Williams <st...@kromestudios.com>]

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.

-- 
Sly



This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Project based authentication

[Nico Kadel-Garcia <nk...@comcast.net>]

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