Re: To get this straight...

["Aaron D. Turner" <aturner@pobox.com>]

-----BEGIN PGP SIGNED MESSAGE-----


On Thu, 4 Mar 1999, Micah Yoder wrote:

> How about this... we have a seperate script directory for each role ID
> (they'll contain both perl and PHP scripts):
> 
> / - no role checking - anyone can access anything
> /role1 - scripts in here require RoleID 1 or greater
> /role2 - 2 or greater
> /role3 - 3 or greater
> etc

I wouldn't call them role1, role2, etc. but yeah that's the basic plan.  I
would say:

/comment
/post
/edit
/etc...
 
> Aaron, how soon can you have this set up?  Authentication is of course
> critical to all the other stuff we're doing.  If you can get this
> working I don't need to worry about the password check code anymore.

I'm going to try to have it done this weekend, but no promises.  This is
kinda new territory for me.    The good news is that since it's beind the
scenes you don't need to wait for me to code your scripts.

Today during my lunch break my goal is to:

1) Fix the access permissions on the web server (we're too open)
2) Create the PHP/mod_perl directories (roleID dirs)
3) "Secure" the PHP/mod_perl with Auth::Any
4) Create an authorization zone in the web server "Linux KB Main"

Auth::Any allows you to test your scripts by using ANY user/passwd
combination.  Of course you'll want to use a username in the DB for your
script to work! :-)

This should get everyone with a usable system that with act just like if
the mod_perl auth system was in place (it just won't be secure).

> And you're *sure* we can pass the user handle into the script (Perl &
> PHP) without another DB lookup?

The user handle will be part of the authorization that the web client
sends with each request, so sure.  Basically the script handles the
authentication and authorization of the URL.  Anything beyond that, will
have to be coded in the script.  If you want to look up the real name or
email address, etc, then that will be done via the script, using the
userid that is sent with each request.

There's also some good code to support cookies too, but I'll worry about
that after I have something working.


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNt/+VjM3jpXy1kJtAQHxkwP/R/XwqhR4JoB04AjIVamRGmSJDBG3my5E
QSNZPsFAyaf7h9E2EI0n51/juna9Ve7OM90boa5uRLdcPJ2iOhPRT7CpVaPoGOiG
IqWsQng1GGcVlEOH3X1E/XMoG1JGSkD1fpVOepToTlJsbURxgcFpK+N0+QiEkEwp
e1gAXBLbW6M=
=0znj
-----END PGP SIGNATURE-----