Re: [phpesp-dev] Proposed changes.

[Matthew G. <gr...@mu...>]

On Sun, 2004-02-08 at 18:03, James E. Flemer wrote:
...snip...
> > 
> > 
> > Well, the easiest way to do this would be to add a new auth module for 
> > phpESP, "auth_apache".  That way anyone using the phpesp user db won't 
> > have to migrate, but anyone who wants to can plug in any apache auth 
> > module and be ready to go.  I imagine the "auth_apache" plugin would be 
> > pretty simple (for respondents).
> > 
> > Perhaps the phpESP auth plugin stuff needs to be split into respondent / 
> > designer though.  So that something like auth_respondent=apache_auth, 
> > auth_designer=phpesp would be possible.  What do you think?
> 
> Having thought about this a little more, I think phpESP needs a bit more 
> of an AAA solution.  Well, maybe we can ignore the third "A" 
> (accounting) for now, and just focus on authentication (authN) and 
> authorization (authZ).  I think that we should try to use PEAR::Auth for 
> authN possibly adding to that project to have an Apache pseudo-"storage 
> container".  Then we need a simple but flexible authZ system.  Right now 
> authN and authZ are all rolled up into one, which makes it difficult to 
> leverage existing authN systems.  With separate "modules" one could 
> easily get authn with ldap/apache/etc, but use (a subset of) the 
> existing phpesp database for authz, or write a new authz module.
> 
> Or maybe we should make a PEAR::AuthZ module that is designed around 
> PEAR::Auth.
> 
> Comments?
Erg.. you make stuff hard :-)
I'll read up on PEAR::Auth and think about this.


> 
> -James
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
-- 
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)