Re: [request] auth_user again

> if it's possible to extend the auth class to provide either an additional > table, or additional fields (which would involve extending the container > classes) as i wrote earlier - at least sql contain er reads additional data from the table with user name and password (less than 10 new lines required in container to fully take advantage of it), but creating additional tables may not be so easy to adapt. > I have a system working that allows for a chain of inheritance from one > user to another. > a user record has a groupID, or a group table could be created > CREATE TABLE group ( > username varchar(255), > groupUsername varchar(255) > ) > > using a separate table for user group associations would allow a user to > belong to more than one group. Or, as another option, the permission > system could restrict group entries to only one per username thus making > permission inheritance a reality. The last is the way I prefer to work. permissions inheritance can be made much simpler and will be enough in most cases: define('writer', 1); define('admin',2); [...] $auth->setPerms(writer | admin); don`t you think it will be enough for 90% of developers? i thought about simple solution that will allow to simply create few access levels and use them. i think i`ll write the code and send to the list for review - i have a really simple solution in mind. > a user interface i've created for just such a system is shown here: > http://www.smur.net/images/screen1.png > this was rendered in netscape 6.2. sure, but have in mind that everyone should create such interface and this is too much work for somebody who only needs basic functionality given by dividing users into 'anonymous' and 'admins'. my idea is much simpler, maybe we should think about creating both complex and simple user permissions managment classes. > well... > this is my two cents worth... > i don't know if this is the direction you're wanting to head in, but this > type of system is serving me quite well for a complex intranet site i'm > developing. i think your idea is a nice one, but in most cases using it would be to much trouble to create start environment to use. creating new tables and adding hierarchy can be to hard to explain for someone who never needed so much from perms class. rash