RE: [Phplib-users] auth url question

[Rob H. <rob...@ws...>]

Why do all three need to be run, the example that I sent handles all three,
but it does so in a structured fashion.  The only one that gets run is what
is asked for.  And that is the whole point.  Auth should try only what it is
inetentionally told to try.  Not try everything until something works...

> -----Original Message-----
> From: Giancarlo [mailto:gia...@na...]
> Sent: Thursday, October 31, 2002 4:08 PM
> To: rob...@ws...
> Cc: Phplib-Users
> Subject: Re: [Phplib-users] auth url question
>
>
> Il 15:23, giovedì 31 ottobre 2002, Rob Hutton ha scritto:
> > The more I think about this, the less I agree, because I think that auth
> > logic was/is flawed.  But attached is a version that I think
> will drop in.
> >
> > IMHO, auth should have a definite structure.  It should not be something
> > where this and that gets tried until something happens to work.
>  And in the
> > case of registration, you could type an existing user name and
> password and
> > get in.  And that is not acceptable on a site that deals with
> credit cards,
> > or business presentation, or a lot of things.
>
> auth_validatelogin and auth_doregister are in userland local.inc.
> A register
> form and a auth_doregister function is not even provided as an example.
> Add an input field to the register form, eg
> <input name=action value=register> and test it in auth_doregister.
> Same for validating the login, add
> <input name=actio value=login> in the loginform and test it in
> auth_validatelogin.
>
> Otherwise we cannot simply call auth->start and pretend it will do, by
> itself, any/everything needed. We'll need to call the three main start
> functions separately, as auth->start(authenticate), auth->start(login),
> auth->start(register). And this is definetely what I'd prefer.
>
> G
>
>