You are here
Rik Goldman - Tue, 2011/07/26 - 18:28
I'm doing something egregious, I think; I'm working on a project without looking to see what progress has been made on it, if any, in the past:OpenLDAP appliance. I think I'm reconciled with this because it's a weak spot for me and a really weak spot for my organization.
My goal is to be able to patch an existing LAMP appliance running several patched applications so that I can have my students login to each appiance with the same login.
I've done a build with web front ends and the openLDAP suite, which was a bit more than I can handle at once.
So I'm going to post in stages.
Forum:
Web Front Ends
Using the LAMP appliance as a starting point (possibly I should remove mysqld).
These build notes take care of the installation and initial configuration of two php-based web front ends: phpLDAPadmin and LDAP Account Manager.
Why two? 1) I haven't the knowledge to evaluate; 2) LDAP Account Manager has a pro and a con: pro, it's in the repos; con, it's hobbled so one must pay for full features. Since I know nothing, I haven't idea of the value of those features; personally, I resent hobbling free software. (3, counting the webmin module.)
This takes care of the hostname, the packages for openLDAP and the initial configuration.
LDAP-Account manager nicely puts its configuration into
conf.d.To force phpLDAPadmin to use SSL I changed 000-default to the following:
A redirect is needed, but I haven't seen the easy path to that yet.
#Please increase the "memory_limit" parameter in your php.ini to at least "64M".
Hey Rik
Adrian did a patch for OpenLDAP some time ago. His notes are pretty comprehensive so may be worth a look to see how he did it - not that it excludes you from having a go at it too. :)
Add new comment