RE: [PEAR-DEV] Another Auth-class

We gave it a long thought too and an idea we came up with would be than an Auth class would be derived from the base User class to handle authentication aspect of a user management system. The base class would handle basic user management aspects like create($first_name, $mid_name, $last_name, $email, $login, $pass) read($login) update($login) delete($login) isRegistered($login) : to be used by the Authentication class for example to know if a user exists (security check up to the developer, ex: login exist or login and email, etc.). The auth class would in charge of the authentication itself. initPassword($login) : in case somebody forgot his password, create and a new one That is still in discussion though. Arnaud. > i was thinking how to integrate this in the auth-classes, since an > authentication is required to determine user rights, which are again > required to give permissions ... > i had thought to extend the Auth_DB-class to enable user management, > but that would mean you have to implement it again for other data > source, so i dropped that idea > putting it in the Auth_common-class seems most logical to me ... any > other opinions? > or writing extra class(es) which only 'use' the Auth? > i dont know ... > > PS: yes, i am talking about the Auth-system i announced here yesterday > > Wolfram >