RE: RE: authentication challenge

> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Tuesday, March 09, 2004 2:46 PM
> Subject: RE: authentication challenge
> Or just set the option permanently in your run-time 'config' file:
>
> [auth]
> store-auth-creds = no

That is probably a good idea for the CLI client, but there is no password caching happening because the client has -never- prompted for a password. It cannot cache what it does not know about...
 
> If tortoisesvn *ever* prompted you for credentials, the svn libraries
> are going to cache them in your personal auth/ area forever after.

TortoiseSVN, just like the svn CLI, has -never- prompted me for a password.

> You'll need to delete the cache. The book has a whole section (in
> chapter 6) about credential caching on the client side. Read
> all about it.

I have read and re-read this entire chapter several times. I do *NOT* have any cached passwords on either the Linux or Windows boxes. I've checked and rechecked this many times over.

The PROBLEM is that the server is not issuing the auth challenge... or it doesn't know that it is supposed to!

It could be, as you pointed out, that the version is too old. I will continue to check this possibility out, however there doesn't seem to be any version information available for svnserve.

If there is an undocumented switch I would sure like to know what it is.
On a related note, it would be helpful if there were some kind of verbose logging mode that could be switched on to assist in troubleshooting issues like this.

I am confident I will get this sorted, it's just taking up an awful lot of time!

Thanks again for your suggestions.

Regards,

RKF

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 10 00:38:16 2004