Hi Garrett,
Thanks for the feedback. I was using http:// only (not svn://).
Your explanation would account for the problem.
To me, it seems wrong for the cached credentials to override the command
line parameters, if that is indeed the case.
Thanks again,
Mark Johnson
On 5/30/06, Mark Johnson <MaJohnson@corillian.com> wrote:
> I have just upgraded my SVN client from 1.2.3 to 1.3.1 (Windows
client).
> Our server has also recently been upgraded to SVN 1.3.1 (Apache
2/DAV).
>
> Since upgrading, the --username and --password options do not seem to
> work.
> I have done a series of tests, and I see some strange behavior.
>
> For instance if I do:
> svn mkdir --no-auth-cache --username Fred URL -m "message"
> I get different results depending upon the version of the client I am
> using:
> Using client 1.2.3 prompts me for Fred's password, and all is good.
> Using client 1.3.1 the password is not prompted for, and I get an
> access error.
>
> Furthermore, in the Apache access.log file on the server, I see that
> the
>
> username (Fred) is apparently not being passed.
> Instead I see my own username (Mark).
>
> My questions are:
> 1. Where does the username (Mark) come from in this scenario?
> 2. How do I use the --username option with the 1.3.1 client?
--no-auth-cache (as I read the code anyway) seems to prevent the caching
of new auth tokens, but not the reading of ones that are already there.
So if you've already got a cached token for Mark, it will still be used.
As to why it's used instead of the one passed on the command line, I'm
not exactly sure. It sure looks like it should be getting passed down
to the right place. The code doesn't look to have changed substantially
between 1.2.x and 1.3.x. Do you see this over svn://, or just http://?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 2 23:56:42 2006