Version Control with Subversion

This is the Title of the Book, eMatter Edition

Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.

124

|

Chapter 6: Server Configuration

Again, the runtime servers file allows you to automate this challenge on a per-host

basis. Either or both pieces of information can be described in runtime variables:

[groups]

examplehost = host.example.com

[examplehost]

ssl-client-cert-file = /path/to/my/cert.p12

ssl-client-cert-password = somepassword

Once you’ve set the ssl-client-cert-file and ssl-client-cert-password variables,

the Subversion client can automatically respond to a client certificate challenge with-

out prompting you.

*

Authorization Options

At this point, you’ve configured authentication, but not authorization. Apache is

able to challenge clients and confirm identities, but it has not been told how to allow

or restrict access to the clients bearing those identities. This section describes two

strategies for controlling access to your repositories.

Blanket access control

The simplest form of access control is to authorize certain users for either read-only

access to a repository, or read/write access to a repository.

You can restrict access on all repository operations by adding the

Require valid-user

directive to your <Location> block. Using our previous example, this would mean

that only clients that claimed to be either

harry or sally, and which provided the

correct password for their ...