Geek Answers Handbook

Subversion Proxy Authentication

Since version 1.5 Subversion supports the presence of a local caching proxy for the main Master repository.

I got the slave synchronization, and the master replayes the commits with the slave. So far, everything is working fine, but now I'm wondering how to do authentication (working with this guide).

When both the master and the slave are authenticated, the slave asks for a username / password when reading, but both asks when writing.

How can authentication be ensured for a slave user (which means that only 1 authentication is independent if it is read or written)?

I am testing with

  • Apache / 2.2.3, Subversion 1.4.2 on a slave device (Debian)
  • Apache / 2.2.8, Subversion 1.5.1 (Ubuntu)
+5
source share
2 answers

In the end, the problem was resolved by setting mod_proxy correctly. Ones mod_proxy knows that it also needs to proxy authentication credentials, it works fine, and the user only needs to enter username / password once.

+2
source

Remember that the password must match the svn client you are using, why would you ask again if you told him to remember it?

You can also read apache, in particular the Require directive, which controls HTTP authentication: http://httpd.apache.org/docs/2.2/mod/core.html#require

Commonly used Require valid-user

+1

More articles:


All Articles