LDAP Administration console is a web-interface that provides a secure, attractive, and user-friendly user interface to maintain and administer OpenLDAP in addition to user accounts, groups, etc in an OpenLDAP directory.
Be the first to post a text review of LDAP Administration Console. Rate and review a project by clicking thumbs up or thumbs down in the right column.
Anyone who has looked at the code thus far has probably noticed that it's somewhat all over the place. (I often code in the same spare time that I drink...) I have been working recently to reorganize the structure to make modular development of additional features easier. As I was being bogged down in the creation of additional features myself, it seemed rather obvious that others would as well. Also of note, I may be having another developer join the project soon; I'm still working on twisting his arm. (Hoping this mention may aid my cause) Also, if anybody is interesting in joining the project, feel free to send patches, recommendations, etc. I must warn you though that some of my code in this is fairly ugly. (feel free to fix it!!! 8-) ... )
For anyone who has been testing or working on this project, please be aware that we have received a valid OID for use in the LDAPadmin schema. Please update your schema definitions with the following OID: objectidentifier LDAPAdmin 1.3.6.1.4.1.24279.0 This has no potential clash with other OIDs (unless somebody has used it inappropriately)
I've recently been busy with updates to ldapadmincon, including an LDAP configuration base template for OpenLDAP 2.3 (using LDAP to update the configuration, and providing an ldif format "base configuration" to get new directories started) I have portions of this under cvs and will be submitting quite a bit more over the upcoming weeks. This will mark a significant milestone in the development of this project as not simply providing a user-add/delete/lock/ -- group-add/delete interface, but a true OpenLDAP configuration interface. I also have some work for existing 2.2 OpenLDAP deployments with flat slapd.conf files, but as yet have not found a satisfactory way of maintaining them. (currently I'm doing it via include directives in the main slapd.conf, and then grouping all configuration entities related to a specific function/part of the openLDAP config in a seperate file, _however_ this is proving problematic when the configuration is updated to 2.3, as when slapd sees the "include" directive, it ldif's the "include" instead of the contents of the included file. (making future configuration changes via LDAP impossible...) I believe I may simply write a pre-compiler to produce a final "slapd.conf" based on the disparite files; which would keep the code to maintain each bit unchanged... more thought is required on this. ... but perhaps 2.3 will become the "stable", and widely used branch before the need arises for ldapadmincon to maintain 2.2 configurations 8-) (yes, that's an affirmative argument to procastinate... ) Also, I am looking for developers to join this project, please contact me if you have any experience in writing AJAX driven web-UI, OpenLDAP configuration scripting, or packaging. (or just want to help)
0.1.2a is a functional release, supporing user and group administration. While many of the advanced features are still missing from this release, it is still quite useable.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?