Posted by: Anonymous Coward
on October 31, 2005 01:04 PM
Um, phpldapadmin.
It's been around for quite some time and is in constant active development. It has a templating system for common objects (such as managing users / groups.) There are also plugins for webmin (which suck IMHO.)
Use google. There are NUMEROUS LDAP admin tools out there. Some are great - others suck.
I'm working on a web-based admin tool for LDAP in perl (don't really care for PHP. And yes, it uses TLS to connect to the LDAP server.) It should be ready soon (I'll create a SF project for it.) There is really nothing wrong with web-based tools if they are written correctly. With a good web tool, I can manage everything I need to via a simple web browser wherever I am.
Some people go all out and try to do everything in LDAP. Services? Hosts? screw that! There is no reason to put those in LDAP. Use it for what it is really good at - user, group, and contact management.
I've got cetralized auth for all applications across all machines - web (modauthldap, tiki, webdav, etc), email (exim, courier, squirrel), logins (ssh, ftp, etc.), and more all via LDAP. Quite nice. Blows the old system away where many things had independant password files, and you had to rdist stuff around all the time. Addnig a new user was an hour long process and is now a 2 min process.
As another comment to a different thread - WTF would you store salary info in LDAP??? Ldap is NOT a generic DB for all info despite what it appears to be. Some things just don't belong in ldap.
Re:Holy Cow! That's Easy?
Posted by: Anonymous Coward on October 31, 2005 01:04 PMIt's been around for quite some time and is in constant active development. It has a templating system for common objects (such as managing users / groups.) There are also plugins for webmin (which suck IMHO.)
Use google. There are NUMEROUS LDAP admin tools out there. Some are great - others suck.
I'm working on a web-based admin tool for LDAP in perl (don't really care for PHP. And yes, it uses TLS to connect to the LDAP server.) It should be ready soon (I'll create a SF project for it.) There is really nothing wrong with web-based tools if they are written correctly. With a good web tool, I can manage everything I need to via a simple web browser wherever I am.
Some people go all out and try to do everything in LDAP. Services? Hosts? screw that! There is no reason to put those in LDAP. Use it for what it is really good at - user, group, and contact management.
I've got cetralized auth for all applications across all machines - web (modauthldap, tiki, webdav, etc), email (exim, courier, squirrel), logins (ssh, ftp, etc.), and more all via LDAP. Quite nice. Blows the old system away where many things had independant password files, and you had to rdist stuff around all the time. Addnig a new user was an hour long process and is now a 2 min process.
As another comment to a different thread - WTF would you store salary info in LDAP??? Ldap is NOT a generic DB for all info despite what it appears to be. Some things just don't belong in ldap.
#