Re: non-interactive user authentication

> If you do
>
> $ svn --username=foo --password=bar
>
> and the values are wrong (i.e., they do not successfully
> authenticate), should Subversion prompt, or should it just fail right
> away?

Fail, IMO. But there is another issue I don't think has been mentioned
yet - that of already checked out copies.

I don't remember what the current behavior is, but how svn should act is
a difficult question.

Is it currently possible to created a checked out version of a
repository that stores the username and URL, but not the password (or
will it be possible in the future)? If so, is the normal expected
behavior for svn to prompt, or to fail saying a password needs to
be provided? If the former, it should be possible to disable it.
But then it is easily forgotten until you run into it.

Another issie is if the username and password on the server has become
invalid since the last time you used the repository. Will svn prompt or
fail?

Perhaps SVN should never prompt unless given explicit instructions to do
so? That way its behavior is more consistent "by default", and there is
one less trap to fall into with respect to bullet proof scripting.

(To be nice to users, it could fail with a message indicating what to do
in order to enable prompting.)

-- 
/ Peter Schuller, InfiDyne Technologies HB
PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@infidyne.com>'
Key retrival: Send an E-Mail to getpgpkey@scode.org
E-Mail: peter.schuller_at_infidyne.com Web: http://www.scode.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org