Re: Anybody working on SSO class/project ???

On Sat, 1 Jun 2002 20:16:05 +0200 (CEST), Markus Wolff wrote: >Tomas V.V.Cox said: >> Nicolas Hoizey wrote: >>> >>> Hi everybody, >>> >>> I'm currently trying to design a PHP SSO (Single Sign On) >>> application, and would like to know if anybody has already done >>> anything. >>> >>> I haven't found any SSO project in PHP yet, but I think it should >>> be part of the Auth package. Some people tried to design a User >>> class a while ago, but I don't know if it has given anything. >> >> I don't think it should be part of Auth, I'd say to use it as part >> of the "User" thing. > >unfortunately I must have missed the start of this discussion... Nicols' email, on which Tomas replied, was basically the start of the discussion. BTW: You can always browse/search the archive of the PEAR mailing lists on http://news.php.net/ and http://marc.theaimsgroup.com/. >what´s the "user" thing? Some time ago we discussed about a flexible system to manage permission handling and we came to the conclusion that this shouldn't be integrated in the Auth package but that it should be a package on its own. After that discussion took place, there were no news lately, but right now it seems as if the topic emerged from the dust again :). >I´ve invested quite some time in this topic >and have already built a user and access rights management class that >is very flexible so that it can easily integrated into the most >different applications. > >[...] > >It has PHPDoc-Style API documentation and is close to PEAR coding >standards. If there´s interest in this kind of class(es) I´ll put it >up for evaluation. I also developed such a thingie for the company I'm working for and we are using it in several applications. It supports different storage containers and so on and I'll review it if we can re-use something for PEAR::User (or however the package will be called). >This depends on how you define user data. What information would you >like to store about the user? When I think of User management, I consider permission handling as an integral and the perhaps most important task. Apart from that it would be nice to store the personal information (email address, day of birdth, social number, number of current girlfriends etc.). But actually it should be possible to also store additional data on a per-application base: Some applications might need a way to store personal preferences, prefered HTML theme etc. for personalized websites and so on. - Martin -- Martin Jansen, <mail@martin-jansen.de> http://www.martin-jansen.de/