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.

Clifton Griffin

Having a single login for every service is a must in large organizations. This plugin allows you to integrate WordPress with LDAP quickly and easily. Like, really really easy.
Contributing 
This is a community project now. Most development is done by users like you who find bugs and fix them, or find new ways to make the plugin more powerful for everyone.
The easiest way to contribute to this plugin is to submit a GitHub pull request. Here’s the repo: 
https://github.com/clifgriffin/simple-ldap-login
Support
If you need support, file an issue here: 
https://github.com/clifgriffin/simple-ldap-login/issues
Special Requests
If you need a customization or change specific to your install, I am available for hire. Shoot me an e-mail: clifgriffin[at]gmail.com
<h4>Features</h4>
<ul>
<li>Supports Active Directory and OpenLDAP (and other directory systems which comply to the LDAP standard, such as OpenDS)</li>
<li>Supports TLS</li>
<li>Uses up-to-date methods for WordPress authentication routines.</li>
<li>Authenticates existing WordPress usernames against LDAP.</li>
<li>Can be configured to automatically create WordPress users for valid LDAP logins.</li>
<li>You can restrict logins based on one or more LDAP groups.</li>
<li>Intuitive control panel.</li>
</ul>
<h4>Architecture</h4>
Simple LDAP Login adds an authentication filter to WordPress that authentication requests must pass. In doing so, it makes several decisions.
<ul>
<li>Can the provided credentials be authenticated against LDAP?</li>
<li>
<ul>
<li>If so, is the LDAP user a member of the required LDAP groups (if any)?</li>
</ul>
</li>
<li>
<ul>
<li>
<ul>
<li>Does a matching WordPress user exist?</li>
</ul>
</li>
</ul>
</li>
<li>
<ul>
<li>
<ul>
<li>
<ul>
<li>If so, log the user in.</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li>
<ul>
<li>
<ul>
<li>
<ul>
<li>If not, is user creation enabled?</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li>
<ul>
<li>
<ul>
<li>
<ul>
<li>
<ul>
<li>Create the user and log them in.</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
This is high level overview. This should answer the philosophical questions about how the plugin works. If the plugin is unable to authenticate the user, it should pass it down the chain to WordPress. (Unless LDAP Exclusive is turned on, in which case it won’t.)

Simple LDAP Login

Integrating WordPress with LDAP shouldn't be difficult. Now it isn't. Simple LDAP Login provides all of the features, none of the hassles.

WP-LDAP vs Simple LDAP Login