
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
120
|
Chapter 6: Server Configuration
and group that owns your Subversion repository. There is no single correct way to
set up your permissions, and each administrator will have different reasons for doing
things a certain way. Just be aware that permission-related problems are perhaps the
most common oversight when configuring a Subversion repository for use with
Apache.
Authentication Options
At this point, if you configured httpd.conf to contain something such as:
<Location /svn>
DAV svn
SVNParentPath /usr/local/svn
</Location>
...then your repository is anonymously accessible to the world. Until you configure
some authentication and authorization policies, the Subversion repositories you
make available via the Location directive will be generally accessible to everyone. In
other words:
• Anyone can use their Subversion client to checkout a working copy of a reposi-
tory URL (or any of its subdirectories).
• Anyone can interactively browse the repository’s latest revision simply by point-
ing their web browser to the repository URL.
• Anyone can commit to the repository.
Basic HTTP authentication
The easiest way to authenticate an client is via the HTTP Basic authentication mech-
anism, which simply uses a username and password to verify that a user is who she
says she is. Apache provides ...