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

Apache and Radius Authentication

From: David Heppenstall <David.Heppenstall_at_rci.rogers.com>
Date: 2006-03-02 22:31:23 CET

Hello,

I'm having some problems serving Subversion repositories over Apache in
conjunction with RADIUS authentication.

I have followed the instructions in Chapter six of the SVN book and have
managed to get this working no problem:
<Location /svnbackdoor>
  DAV svn
  SVNParentPath /opt/svn
</Location>

In addition, I have added the FreeRadius mod_auth_radius module to
Apache and have also managed to get this working:
<Location /securetest>
  AuthType Basic
  AuthName "RADIUS authentication for no reason other than to annoy
you."
  AuthAuthoritative off
  AuthRadiusAuthoritative on
  AuthRadiusCookieValid 5
  AuthRadiusActive On
  require valid-user
</Location>

I assumed that just by concatenating these two fully-functioning
configurations that I would have a working RADIUS-Authenticated
Subversion url:
<Location /svn>
  DAV svn
  SVNParentPath /opt/svn
  AuthType Basic
  AuthName "RADIUS authentication."
  AuthAuthoritative off
  AuthRadiusAuthoritative on
  AuthRadiusCookieValid 5
  AuthRadiusActive On
  require valid-user
</Location>

As you can see, all I did was put the options together in the same
<Location> directive. However, when I try to view the url in a web
browser, I am presented with a 404 error after entering a correct
username and password. In the CLI client, I get this:
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 405 Method Not Allowed (http://<ip-removed>)
I speculate that once RADIUS authentication is completed, the request is
interpreted to be a literal filesystem path within DocumentRoot and my
SVNParentPath instruction is ignored.

The only way I have managed to get *some* of this working is by setting
DocumentRoot to "/opt/svn" and the SVN Location directive to "/". What
happens in this case is that the web browser can view repositories
perfectly after being authenticated. However, the CLI client returns a
301 Moved-Permanently error. I've read in the FAQ that this is an
expected problem when the SVN location overlaps with the DocumentRoot.
My DocumentRoot is now set to something completely different (/var/www/)
to avoid this problem, however now I'm back to being stuck with the 404
errors.

I would very much appreciate any pointers, assistance or guidance you
may have.

Thank you.

 - Dave Heppenstall
   david.heppenstall AT rci DOT rogers DOT com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 2 22:33:13 2006

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