Plugin Directory

Test out the new Plugin Directory and let us know what you think.
!This plugin hasn’t 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.

WPMU Ldap Authentication

A plugin to override the core WordPress authentication method in order to use a LDAP server for authentication. Currently only supported on MultiSite


Alistair Young - Original LDAP Plug-in http://www.weblogs.uhi.ac.uk/sm00ay/?p=45

Patrick Cavit - WordPress 1.5.1 Modifcation of LDAP Plug-in http://patcavit.com/2005/05/11/wordpress-ldap-and-playing-nicely/

Hugo Salgado - WordPress 2.0.3 Patch of WordPress 1.5.1 Modifcation of LDAP Plug-in http://hugo.vulcano.cl/development/wordpress/ldap-auth-patch/

Alex Barker - WordPress MU 1.0.* Modifcation of LDAP Plug-in http://wpmudev.org/project/WPMU-LDAP-Authentication-Plug-in

Dexter Arver - Windows LDAP Support Contribution for WordPress MU 1.0.* LDAP Plug-in

Sean Wedig - http://www.thecodelife.net/category/software-dev/technology/wpmu/wpmu-ldap/

Aaron Axelsen - http://www.frozenpc.net

How It Works

When enabled, this plugin can automatically create WordPress user accounts and blogs for LDAP-authenticated users. Assuming user credentials authenticate against the LDAP server, creating local accounts and blogs follows this algorithm:

Create a new WPMU User, with LDAP username and a randomly generated password. Some user information, such as first and last name, is extracted from the information returned from the LDAP server. Actions for user creation and activation are triggered. The user's domain / URL are created depending on plugin configuration (i.e., VHost vs SubDir). If the option is set, a blog is created, with path and name based on the LDAP username and the blog is activated with the user being Administrator, and appropriate actions are triggered.

It should be noted that even though a random password is created for a user (for WPMU accounts), it is never displayed to the user. This is intentional so that there is no confusion as to which password should be used; it will always be using LDAP credentials. As a result, though, if ever LDAP is disabled or if the server is unavailable, users created with LDAP authentication will be unable to log in unless their passwords are reset.

Requires: 3.2 or higher
Compatible up to: 3.4.x
Last Updated: 4 years ago
Active Installs: 30+


4.3 out of 5 stars


Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.

0,1,0 100,1,1