Re: non-interactive user authentication

On Monday, October 7, 2002, at 12:07 PM, Karl Fogel wrote:

> There's still the question of how to behave when updating a working
> copy that has auth info which is no longer valid on the server.

The rule still applies. If auth info is specified on the command line,
use that info to authenticate. If authentication fails, the command
fails with an appropriate error. Otherwise, prompt.

I leave the question of whether to update the working copy to others.

> Let me expand this to the general problem:
>
> Subversion has some commands that, in some circumstances, can prompt
> the user for information. Any script that runs such commands may need
> a `--non-interactive' option to suppress the prompting, because the
> script can't always control whether or not the prompt-causing
> circumstances will arise.

Ah, this is a problem. The "explicit-auth" rule only works if the
prompting is necessary because of failed authentication. A script
shouldn't have to supply auth information for commands that don't touch
the repository. In that case, a --non-interactive flag is, indeed,
necessary.

> We can get rid of the option, but only if we also *never* prompt as a
> default fallback behavior.
>
> Do we want that?

Beats me.

Colin Putney
Whistler.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 7 21:45:32 2002