Re: Another Auth-class

LIMBOURG Arnaud wrote > M, sorry to ask the question again but I said we started a user > management system, is anybody interested in that or is it > completely useless ? i thought of extending my Auth-classes to end up with something like a user management system, which in my eyes at least has to have some kind of permissions, like admin, users maybe groups methods which implement: register, changeData, email-info ... so on matching actions to permissions (like: only admin can delete users...), etc. 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