Hi Bert, Firstly, thanks for the reply. It seems that deleting the cached credentials and recreating them, did the trick.
I (obviously) didn't ever manually create the cache or edit it myself. I assumed that changing to the new URL would simply create a new credential "set" for that URL and was, thus, surprised when it kept asking me to authenticate with any svn operation. I don't know if that is expected behaviour or perhaps a bug that needs some attention? As always - thanks! Gavin. On 30/09/2011, at 6:17 PM, Bert Huijben wrote: > Passwords are stored per hostname (+realm), not per working copy like in your > webbrowser, so using a different hostname requires adding a new > username+password in your credential cache. > > Storing it in a different way would allow tricking subversion to send the > username and password to any other server… > > Bert > > From: Gavin Baumanis [mailto:gav...@thespidernet.com] > Sent: vrijdag 30 september 2011 5:14 > To: Subversion Users > Subject: Authentication realm > > Hi Everyone, > > We recently created a DNS entry for our subversion repository. > Prior to this we just use the private LAN IP address to access the repo via > http (Apache) > > Post the change to having a hostname to use I created a new branch - and used > the host name to do this. > > Subsequently when I perform an svn update I a now prompted for username and > password for the named instance of our repo. > I did some reading in the "good" book. > and used svn switch > (svn switch old_IP_address new_HostName_Address > > at the root of my working copy. > svn info confirms that the repo address is now set to the hostname version of > the URL. > > However I am still getting prompted for a username and password. > If I enter the "usual" password - all is good... but the prompt is playing > havoc without Continuous Integration scripts. > > Some more reading suggests that I might need to add a new authentication > realm and users via; conf/svnserve.conf > > I was hoping that I might just get some confirmation that is indeed what I > need to do - before I go "playing" with the config scripts. > > As always - a big thanks for your help. > > Gavin.
