Re: svn commit: rev 4685 - in trunk/subversion: include libsvn_wc libsvn_client libsvn_auth

"Sander Striker" <striker@apache.org> writes:

> > More issue #724 - Some fixes, and now only try to save using the
> > provider that supplied the creds.
>
> Huh? I really don't get this. A simple prompting provider won't
> be able to save creds, so if a passwd is not in a cache it has no
> chance of ever getting in? My take on this was try the provider
> you got the creds from first, if that fails cycle over all others.

Our simple prompting provider can, because it uses the same
auth-storing function that the WC-cache-reading provider uses.

> This can be done in the phase where we register the providers. If
> --no-auth-cache is present, simply not register the provider that
> gets/sets the user/pass in the working copy. And do register it
> if store-password is present.

I think WC auth-reading provider should be registered even if
'store-password' is "no". Just because the user no longer wants us to
store his password doesn't mean it isn't already in the cache. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 31 09:56:02 2003