I'm running 1.0.8 and I don't get the expected behavior for per-directory
access control. Here is the expected error for a user trying to commit to
a directory in which they only have read access:
svn: Commit failed (details follow):
svn: CHECKOUT of /svn/SVNREPO/!svn/ver/21/mcp750/trunk/project.env:
authorization failed (https://paciencia)
Now, here's the unexpected error when a user with read and write privileges
tries to commit to that same directory.
Transmitting file data .svn: Commit failed (details follow):
svn: PUT of
/svn/SVNREPO/!svn/wrk/d77c038d-85e7-0310-8bcb-c353c4a2ff2e/mcp750/trunk/project.env:
501 Method Not Implemented (https://paciencia)
Here's my subversion config file that sets up the per-directory access
control from my web server:
subversion.conf
===============
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so
<Location /svn>
DAV svn
# Parent directory, below which are the various Subversion repositories
SVNParentPath /proj
# Authentication method for user
AuthType Basic
AuthName "Internal Access"
AuthUserFile /var/www/access/www-passwd
# Restrict user access within the Subversion repositories
AuthzSVNAccessFile /var/www/access/authzfile
# Only allow authenticated users
Require valid-user
</Location>
And here's my Authz file that specifies access privileges for the users.
Authz file
==========
[groups]
developer = harry, sally
svnadmin = tom
[/]
* = r
[SVNREPO:/]
@svnadmin = rw
@developer = r
[SVNREPO:/mcp750]
@svnadmin = rw
@developer = r
[SVNREPO:/mcp750/trunk]
@svnadmin = rw
@developer = r
[SVNREPO:/mcp750/branches]
@svnadmin = rw
@developer = rw
Is there something that I'm forgetting to do? I am planning to host
multiple subversion repositories off my secure web server and that is why
I'm using SVNParentPath.
- David
At 05:00 PM 10/26/2004 -0500, Ben Collins-Sussman wrote:
>On Oct 26, 2004, at 12:27 PM, David Henriquez wrote:
>
>>I've been searching the mail list archive and I found the emails listed
>>below that describe the problem that I'm having. It seems that earlier
>>versions of Subversion web interface (i.e. mod_authz_svn) did not support
>>using SVNParentPath with per-directory access control. Is there a
>>version that fixed this or is this bug still TBA?
>
>This bug only existed in 1.0.0. It was fixed in 1.0.1, last March, about
>two weeks after the 1.0.0 release. You're about eleven releases behind. :-)
>
>See the CHANGES file:
>
> http://svn.collab.net/repos/svn/trunk/CHANGES
***************************************************************************************************
David A. Henriquez
Simulation and Verification Group (3458)
Autonomy and Control Section
Jet Propulsion Laboratory
4800 Oak Grove Dr. 198-235, Pasadena, CA 91109-8099
work: (818) 354-5920
cell: (818) 281-5240
fax: (818) 393-5007
email: David.Henriquez@jpl.nasa.gov
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 28 20:13:56 2004