[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: libsvn_auth

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2003-02-05 00:50:30 CET

Ben Collins-Sussman <sussman@collab.net> writes:
> * get ra_local to stop using the old auth system.
>
> --> it wants to pull a username; does this mean writing two
> new providers (wc and prompt) just for the "username" kind
> of credentials? Or maybe just one big provider that tries
> all four methods on successive attempts (cmdline arg, disk,
> getuid, prompt)? I'm leaning toward the latter.

(I might be just confused, but...) I thought the whole point of the
multiple-providers-per-credential-type was precisely so we could write
different providers here and try them in a loop. That way, if we
learn some new method of getting "username"-style credentials, we just
write a new provider, i.e., we don't have to ponder the question "Does
this become a new kind of attempt in our one big provider, or should
it get its own provider?", because the answer is "It gets its own
provider."

Oh, but... I think I see. There's no point retrying the
args/disk/getuid stuff again, because it either worked or it didn't.
Only prompt should be retried. So that seems to imply at least two
providers: an args/disk/getuid provider, and a prompt provider. But
then there has to be some state bit that says not to retry with the
first provider (or to have it return early failure), because retrying
those creds would be a waste of time.

My head hurts :-). It may be that I'm missing something here; I'll
ask you when you get here tomorrow, save us some typing and save the
list some noise.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 5 01:20:40 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.