Meitar

This plugin turns your WordPress Dashboard into a familiar management interface for an enterprise-scale LDAP Directory Information Tree (DIT). Configure a connection to your LDAPv3 directory server, and from then on any modifications you make to your WordPress user database through the WordPress admin screens will be reflected in your LDAP database. This offers a simpler and more convenient front-end for managing user account information to support single sign-on (SSO), identity management, and other enterprise functions.
Donations for this plugin make up a chunk of my income. If you continue to enjoy this plugin, please consider <a href="https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=TJLPJYXHSRBEE&lc=US&item_name=WP-LDAP&item_number=WP-LDAP&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted" rel="nofollow ugc">making a donation</a>. 🙂 Thank you for your support!
All user accounts on the WordPress side are mirrored as <a href="https://www.ietf.org/rfc/rfc2798.txt" rel="nofollow ugc"><code>inetOrgPerson</code> (RFC 2798)</a> entries on the LDAP side. The following WordPress user account fields to LDAP attribute translations take place when a new WordPress user is created:
<ul>
<li>The WordPress <code>user_login</code> field becomes the <code>uid</code> attribute in the LDAP database.</li>
<li>The WordPress <code>user_email</code> field becomes the <code>mail</code> attribute in the LDAP database.</li>
<li>The WordPress <code>display_name</code> field becomes the <code>displayName</code> attribute in the LDAP database.</li>
<li>The WordPress <code>user_pass</code> field becomes the <code>userPassword</code> attribute in the LDAP database.</li>
</ul>
There is no mapping for the WordPress user ID number on the LDAP side. Instead, users are uniquely identified by their fully-qualified Distinguished Name (DN). A user’s DN is automatically composed by combining their WordPress <code>user_login</code> with the WordPress Multisite’s configured LDAP Search Base setting. For instance, by default, a WordPress Multisite with WP-LDAP installed running at <code>https://example.com/</code> with a user whose username is <code>exampleuser</code> will automatically be mirrored over LDAP to the user identified as <code>uid=exampleuser,dc=example,dc=com</code>.
In addition to the above mappings, the following optional mappings also take place if or when the user updates their user profile:
<ul>
<li>The WordPress <code>first_name</code> field becomes the <code>givenName</code> attribute in the LDAP database.</li>
<li>The WordPress <code>last_name</code> field becomes the <code>sn</code> attribute in the LDAP database.</li>
<li>The WordPress <code>nickname</code> field becomes the <code>cn</code> attribute in the LDAP database.</li>
<li>The WordPress <code>description</code> field becomes the <code>description</code> attribute in the LDAP database.</li>
<li>The WordPress <code>user_url</code> field becomes the <code>labeledURI</code> attribute in the LDAP database.</li>
<li>The WordPress user’s avatar becomes the <code>jpegPhoto</code> attribute in the LDAP database. (Not yet implemented.)</li>
</ul>
Moreover, WP-LDAP is aware of certain features provided by other plugins. These include:
<ul>
<li>The WordPress user’s S/MIME certificate (<code>smime_certificate</code> field) becomes the <code>userSMIMECertificate</code> attribute in the LDAP database. (This functionality is provided by the <a href="https://wordpress.org/plugins/wp-pgp-encrypted-emails/" rel="ugc">WP PGP Encrypted Emails</a> plugin and that plugin must be installed and activated for this to work.)</li>
</ul>
This plugin is designed for medium to large deployments of WordPress Multisite (or Multi-Network) instances, originally developed as a collaboration with the <a href="https://glocal.coop/activist-network-platform/" rel="nofollow ugc">Glocal Coop’s Activist Network Platform</a> project. If you run multiple WordPress Multisite Networks, you can configure each WP Network with different LDAP settings. This plugin does not currently support single-site installs; please <a href="https://github.com/meitar/wp-ldap/issues" rel="nofollow ugc">post an issue on GitHub</a> if you want to use LDAP data stores with a WP single-site install and we can discuss use cases. 
This plugin is free software, but grocery stores do not offer free food. Donations for this plugin make up a chunk of my income. If you continue to enjoy this plugin, please consider <a href="https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=TJLPJYXHSRBEE&lc=US&item_name=WP-LDAP&item_number=WP-LDAP&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted" rel="nofollow ugc">making a donation</a>. 🙂 Thank you for your support!

WP-LDAP

Translates the WordPress user database to an LDAP store of the same; manage your LDAP DIT using your WordPress Dashboard.

Curtiss Grymala

This plugin allows WordPress to authenticate, authorize, create and update against an Active Directory domain. This plugin is based heavily on the <a href="https://wordpress.org/extend/plugins/active-directory-integration/" rel="ugc">Active Directory Integration</a> plugin, but has been modified to work with Multi Site and even Multi Network installations of WordPress.
Some of the features included in this plugin are:
<ul>
<li>authenticate against more than one AD Server (for balanced load)</li>
<li>authorize users by Active Directory group memberships</li>
<li>auto create and update users that can authenticate against AD 
mapping of AD groups to WordPress roles</li>
<li>use TLS (or LDAPS) for secure communication to AD Servers (recommended)</li>
<li>use non standard port for communication to AD Servers</li>
<li>protection against brute force attacks</li>
<li>user and/or admin e-mail notification on failed login attempts</li>
<li>determine WP display name from AD attributes (sAMAccountName, displayName, description, SN, CN, givenName or mail)</li>
<li>enable/disable password changes for local (non AD) WP users</li>
<li>WordPress 3.0/3.1 compatibility, including Multi Site and Multi Network</li>
</ul>
This plugin is based on <a href="https://wordpress.org/extend/plugins/active-directory-integration/" rel="ugc">glatze’s Active Directory Integration</a> plugin, which is based upon <a href="https://wordpress.org/extend/plugins/active-directory-authentication/" rel="ugc">Jonathan Marc Bearak’s Active Directory Authentication</a> plugin and <a href="http://adldap.sourceforge.net/" rel="nofollow ugc">Scott Barnett’s adLDAP</a>, a very useful PHP class.
Aside from the changes to make this plugin work more effectively with WordPress Multi Site, this version of the plugin also encrypts the password used to connect to the AD server when it is stored in the database.
This plugin was developed by <a href="https://wordpress.org/extend/plugins/profile/cgrymala" rel="ugc">Curtiss Grymala</a> for the <a href="http://umw.edu/" rel="nofollow ugc">University of Mary Washington</a>. It is licensed under the GPL2, which basically means you can take it, break it and change it any way you want, as long as the original credit and license information remains somewhere in the package.
<h3>Important Notice</h3>
Since I don’t currently have access to multiple AD servers, this plugin has only been tested on a single installation of WordPress with a single AD server. Therefore, it is entirely possible that there are major bugs.
At this time, I am seeking people to test the plugin, so please report any issues you encounter.
<h3>Requirements</h3>
<ul>
<li>
This plugin requires WordPress. It might work with versions older than 3.0, but it has not been tested with those.
</li>
<li>
This plugin also requires PHP5. Some attempt has been made to make it compatible with PHP4, but it has not been tested in that environment.
</li>
<li>
This plugin requires LDAP support to be compiled into PHP. If the <code>ldap_connect()</code> function is not available, this plugin will output an error message and will not do anything.
</li>
</ul>
<h3>To Do</h3>
<ul>
<li>Add ability to validate against multiple AD servers (check one, then the other – rather than just load-balancing as the plugin currently does)</li>
<li>DONE as of 0.4a – Update admin interface to utilize native meta box interface rather than custom layout</li>
<li>DONE as of 0.3a – Separate the profile information from the role equivalent groups in the “auto update user” setting</li>
</ul>

Active Directory Authentication Integration

Allows WordPress to authenticate, authorize, create and update users through Active Directory

WP-LDAP vs Active Directory Authentication Integration