[dev] extending Auth

[Jon Parise]

On Wed, Jul 24, 2002 at 07:13:32PM +0200, Tarjei Huse wrote:

> I saw that the admin module uses the Auth object from horde to do it's tasks.
> When I looked at the driver for Ldap and it seemes rather barebone. I'm
> considering extending the driver so I can let som non-technical users use horde
> to add and remove users in a wider setting (samba & posix).
> 
> 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?

If you want to build Auth drivers for samba and POSIX interfaces, that
would be great.
 
> Maybe the best way would be if the addUser function called a number of
> registered modules?  Anyhow just give me some hints on how to do this, I am
> asking so that whatever comes out of it is as "Hordesqe" as possible. :)

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).
 
> I'd like to make a "usertemplatefile" for configuring the user - so that an
> administrator can choose sensible defaults and let the non-technical user only
> worry about username, phonenumber and quotasize (f.x.). 

Moving in that direction would be great.
 
> If there's allready a document describing how to extend the Auth class, please
> lett me know.
 
The source code for the other Auth drivers are probably the best
resource.  You may also want to check out:

    http://dev.horde.org/

-- 
Jon Parise (jon@horde.org) :: The Horde Project (http://horde.org/)