[dev] extending Auth

[Tarjei Huse]

Hi,
<(snip)>
> > Therefore I am wondering what is the best way to extend the admin module.
> > Basicly I am wondering if I should write a new class that extends Auth or
> if it is best using a require inside the function etc. 
> I'm confused about what you're asking.  Are you interested in
> extending the Auth drivers or the admin interface?

goal: Be able to use the admin interface for administering groups and users. 

what is needed: 
a) a way to add a ldap entry that defines:
n number of "modules" (for example samba and POSIX + default groups.)
b) Autocreation of mailboxes.
c) creation of homedir

> If you want to build Auth drivers for samba and POSIX interfaces, that
> would be great.
?? 

Note: Please understand I'm not an expert but I know my way around php and basic
OO - but not all the convetions you use. 

the addUser function in ldap.inc only adds a few things. I'm looking for a way
to extend what is added in the ldap entry and maybe the two others could be
"modules" under the admin section. I don't think it would be as easy to do the
same in sql or mcal :)

> I don't think extending addUser() is the best approach.  The admin
> interface should just instantiate as many Auth instances as it needs
> to get the job done (i.e. one Auth instance for each backend).
se above on the ldap backend. 

Tarjei
  


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/