[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Apache mod_dav_svn Issue: no author

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-06-30 15:45:43 CEST


> The issue is that while we can see the basic auth username for the
> transaction in the apache access log, this username is not being
> populated as the author. This of course results in us seeing no author
> when looking at the resulting repository (via log, info, etc).
> Here is the Apache configuration (from subversion.conf):
> === BEGIN subversion.conf
> LoadModule authz_ldap_module modules/mod_authz_ldap.so
> LoadModule dav_svn_module modules/mod_dav_svn.so
> LoadModule authz_svn_module modules/mod_authz_svn.so
> # Main Repository
> <Location /svn/main>
> DAV svn
> SVNPath /shared/subversion/repos/main
> SVNIndexXSLT "/svnindex.xsl"
> SSLRequireSSL
> # ldap lookup
> AuthzLDAPEngine on
> AuthType Basic
> AuthName "LDAP"
> AuthzLDAPServer
> AuthzLDAPLogLevel warn
> # user lookup
> AuthzLDAPUserBase cn=users,ou=org,dc=abc,dc=com
> AuthzLDAPUserKey uid
> AuthzLDAPUserScope base
> # group lookup
> AuthzLDAPGroupBase cn=groups,ou=org,dc=abc,dc=com
> AuthzLDAPGroupKey cn
> AuthzLDAPGroupScope base
> AuthzLDAPMemberKey uniquemember
> </Location>
> # Protect root level directories - deny write
> <LocationMatch "/svn/main$">
> Deny from all
> </LimitExcept>
> </LocationMatch>
> # under root are three subdirs for organization purposes
> # allow only admins to write to these
> <LocationMatch
> "/svn/main/(Common|Investor.*Services|Securities.*Services)$">
> require group "SVN Administrator"
> </LimitExcept>
> </LocationMatch>

> Prior to posting this message I did search through previous messages on
> this list as well as read through the FAQ. While I did find similar
> issues, it seemed that they all referenced the issue being tied to
> anonymous write access. Our repository is not configured for anonymous
> write (accomplished by the <LimitExcept .... /> within the
> subversion.conf file and evident in that modify operations do prompt the
> subversion client for username and password).

Your access control isn't correctly set up: the *only* way to get
access control set up correctly in conjuction with WebDAV is to use
mod_svn_authz. Using LocationMatch or other - similar - constructs
won't work.

If the problem is that you can't use mod_svn_authz because it doesn't
do wildcards or regexes, then I'd like to point you to the following
patch which does provide that functionality (I posted about that
earlier this week in relation to LOCK requests failing):


> As you can see in the log excerpt above, user123 is identified with the
> MERGE method that occurs as part of this transaction. Yet, there is no
> resulting author entry:

authenticated... At least the authentication data for mod_dav_svn is
rather minimal.

> svn info "https://server.abc.net/svn/main/Securities Services"
> Path: Securities Services
> URL: https://server.abc.net/svn/main/Securities%20Services
> Repository Root: https://server.abc.net/svn/main
> Repository UUID: 6947a9cc-020e-0410-bd0f-a223dbb24b38
> Revision: 6535
> Node Kind: directory
> Last Changed Rev: 6535
> Last Changed Date: 2006-06-29 21:43:18 -0400 (Thu, 29 Jun 2006)
> I would appreciate any help/insight into this issue. I am hoping it is
> a configuration or other easily-corrected oversight; yet, I have already
> considered the possibility of having to write something to grab the
> remote user and throw it into the svn:author property if absolutely
> necessary.

Fixing your configuration would be my advise. If you have time to
address the comments of Branko Cibej on the patch in the link I
referred you to above, this functionality has - IMO - quite a big
chance of being incorporated in mod_authz_svn.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 30 15:47:42 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.