Version Control with Subversion

This is the Title of the Book, eMatter Edition

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

svnserve; A Custom Server

|

111

• The user wants to authenticate as a different user than her system login name.

• A script wants to authenticate without using cached credentials.

Here is a final summary that describes how a Subversion client behaves when it

receives an authentication challenge:

1. Check whether the user specified any credentials as command-line options, via

--username and/or --password. If not, or if these options fail to authenticate suc-

cessfully, then

2. Look up the server’s realm in the runtime auth/ area, to see if the user already

has the appropriate credentials cached. If not, or if the cached credentials fail to

authenticate, then

3. Resort to prompting the user.

If the client successfully authenticates by any of the methods listed previously, it will

attempt to cache the credentials on disk (unless the user has disabled this behavior,

as mentioned earlier).

svnserve; A Custom Server

The svnserve program is a lightweight server, capable of speaking to clients over

TCP/IP using a custom, stateful protocol. Clients contact an

svnserve server by using

URLs that begin with the

svn:// or svn+ssh:// schema. This section explains the dif-

ferent ways of running

svnserve, how clients authenticate themselves to the server,

and how to configure appropriate access control to your ...