Re: graphical LDAP client

[Joseph Hoot <joe@networkpenguin.com>]

ldapAdmin on sourceforge.net.

If you feel like trying it out, I have started to create a simple
ldapAdmin PHP program on sourceforge.net.  It is meant to be useful for
my own company and the LDIF structure that we have created.  It
currently does simply things such as Add Users (with very common
fields), Modify those users, delete users, and allow users to change
their own passwords based on who logs into the program (ACL's are
important here).  This program has recently started and I am in the
process of getting it to work for my company here.  I have tried to
create it with dynamic variables in mind.  Therefore, you can edit a
couple config files and it may work for you.

Since I have not released any files for this yet, you will have to grab
it out of CVS.  And if you are having problems, you can post to the
email list or forum section.

like I said, it is really just a project that I am working on for my own
company and I have tried to design it to allow other copmanies to use
this.  It currently only does things for users.  Plans for Groups, Email
Aliases, and Hosts are in the works....

just thought I'd let ya know.


Michael Ströder wrote:

> Hugo.van.der.Kooij@caiw.nl wrote:
> >
> > On Tue, 17 Oct 2000, Graciela Machado Leopoldino wrote:
> >
> > > I'm new user of OpenLDAP and I would like used a graphical
> > > LDAP client. I tried the Kldap but don't have success and GQ
> > > isn't very good. Is there other tool ?
> >
> > Just what do you expect of it? I haven't seen a
> > do-it-all-in-one tools for LDAP yet.
>
> And IMHO it's really impossible to write a do-it-all-in-one tool.
> Especially for being used by end-users for their daily work. Too
> much knowledge of the directory's data model is needed for using
> generic LDAP clients. You also wouldn't use a generic SQL tool to
> let the secretary maintain a company's address book in your SQL DB.
>
> People often ask me for customization options of web2ldap for
> day-to-day maintenance of address books or a user DB. Although there
> are some of such options already there my answer is always: Write
> your own customized LDAP client for your special needs or pay
> somebody who does it for you.
>
> Ciao, Michael.