Re: Entry Authentication

[jpincin@ashtech.net]

> that come with Apache.  Apache supports DBM user files which provides
> excellent lookup speed with large lists of users (auth_dbm module).  The
> advantages are:
> 2)  No privacy issues assocaiated with cookies.  (Server/browser does the
> tracking auto-magically.)

I'm not sure how this would work for a complex system like we're talking about...
where we have all kindsa permission flags associated with each registered user...

> 3)  Simple to maintain.

Both systems are simple to maintain actually.  We'll have web front ends into the
DB system if thats the way we decide to go.

> Bad:
> 
> 1) Effects MySQL DB?  Not sure.

No... it wouldn't effect the MySQL DB's.  All user info would still need to be
maintained within the tables... we'd have to develop some way to reference
between the MySQL DB's and the DBM userid... they'd have to be identical...
hopefully that would be scriptable... otherwise this would add another level of
possible failure... but as I said... the info would still need to be maintained
in both places... the DB queries/hits would still ned to happen... the only thing
this would avoid would be the cookie/re-entry of username/passwd each time it's
needed.

> 2) Is the userid accessable???  There will probably be other places in the
> site where we will want to leverage this info.

Absolutely... we need to reference the userID every step of the way in our
system... Well... during any interactive part of the site anyway... which'll be
alot.

So... is there a way to reference the userID... or more relevent... does anybody
know how/have an example?

Jason