Having a single login is a must in large organizations. This plugin allows you to integrate WordPress with LDAP for each site.
| Author: | Alex Dekker (profile at wordpress.org) |
| WordPress version required: | 3.3 |
| WordPress version tested: | 3.5.2 |
| Plugin version: | 1.0.0 |
| Added to WordPress repository: | 13-07-2013 |
| Last updated: | 13-07-2013
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 0 |
| Rated by: | 0 |
| Plugin URI: | http://alex-dekker.nl/ |
| Total downloads: | 3 030 |
| Active installs: | 10+ |
Click to start download
|
Having a single login for every service is a must in large organizations. This plugin allows you to integrate WordPress with LDAP for each individual site. You can create different base dn's for every site and still have only one list of users.
First of all this plugin is based upon the simple LDAP Login I made some changes which I think are handy.
When you want to manage multiple single wordpress installations, password management becomes crucial. When someone's password has been cracked you would have to change it everywhere wouldn't it be simpler to just edit it on one place.
Feature request
Do you have an idea to make this plugin better, please let me know leave a message here or email me alex[at]alex-dekker.nl.
Donate?
If you want to donate please email me.
FAQ
Other than WordPress, what does my system require?
- PHP 5
- A LDAP server like openldap or active directory
- PHP must be configured/compiled with ldap support!
How do I know what the correct settings are?
I have tried to make the settings as self-explanatory as possible. If you are struggling figuring them out, you may need to speak with your LDAP administrator. I realize this is an obnoxious response, but there is no good, fail proof way to help you discover these settings. A good place to start, if you’re feeling daring, might be to use ADSIEdit for Windows and Active Directory, or GQ for Linux and OpenLDAP.
It’s still not working, what other things can I try?
If you are confident your settings are correct and it still does not work, it may be time to check for port or firewall issues. If your LDAP server is running on a non-standard port or an obsolete version of the LDAP protocol you are going to have issues. Port 389 is the port this plugin, and nearly every other LDAP enabled software expects. They are also expecting protocol version 3. If you are using an old version of LDAP or running a non-standard port you may need to modify the code that the plugin runs or update your LDAP installation.
Unfortunately I can’t be relied upon to assist with these types of requests. I chose not to support these scenarios because they are infrequent and because they confuse everyone else.
It’s still not working! How can I get help?
There are two ways. You can post a comment on my blog (http://alex-dekker.nl/) or you can e-mail me: alex[at]alex-dekker.nl. I’ll do my best to get you up and running!
ChangeLog
