...
>
> I think you've mixed the Apache auth config and svnserve auth config.
> When serving via Apache, the password file is located using
> AuthUserFile in the <Location> block.
>
> Comment the first 2 lines out of /etc/authz-svn and see what happens.
>
I did this, and the original message "Failed to load the
AuthzSVNAccessFile:" no longer occurs. It still fails to allow login:
Access denied: 'name1' PROPFIND helloworld:/
This same password db file created from htpasswd works without
AuthzSVNAccessFile, so unless Authz and blanket access somehow require
the httpd conf file for "AuthUserFile /etc/passwd-httpd" to be a
different format, it should work. I have double checked that chcon -R -h
-t httpd_sys_content_t has been applied (and since it worked without
Authz it has also been tested). If I intentionally use a wrong password,
it changes in the logs to indicated password mismatch, so I also have to
conclude that the password file is itself being queried correctly. The
directory at /var/www/svn/ and the repo /var/www/svn/helloworld/ are
owned entirely by user and group apache, and have never been touched by
any other user (used sudo as apache while logged in as root to create this).
My httpd conf block again is:
<Location /svn>
DAV svn
SVNParentPath /var/www/svn
SSLRequireSSL
AuthzSVNAccessFile /etc/authz-svn
Require valid-user
AuthType Basic
AuthName "Subversion Repository"
AuthUserFile /etc/passwd-httpd
</Location>
The new authz-svn file:
[groups]
devel = name1, name2, name3, name4
[helloworld:/var/www/svn/helloworld]
name1 = rw
What other permission could be causing failed PROPFIND when this same
setup works without Authz?
D. Stimits, stimits AT comcast DOT net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 22 00:54:21 2007