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.

OrbitaNET

This plug-in extends Simple LDAP Authentication plug-in <a href="https://wordpress.org/extend/plugins/simple-ldap-authentication" rel="ugc">Simple LDAP Authentication</a>. 
Plug-in works as followed:
Entered credentials are checked by all hash types available on LDAP-server (ssha, smd5, crypt/standart-des, crypt/enhanced, crypt/md5, crypt/blowfish, sha, clear, md5) by specified login.
If password is correct:
If user already exist in WordPress database
<ul>
<li>Password, name, surname, e-mail are changed to those existing on LDAP-server.</li>
</ul>
If no such user is in WordPress database:
If automatic user transfer is disabled by plug-in settings:
<ul>
<li>Existing user data is updated</li>
</ul>
If automatic user transfer is enabled by plug-in settings:
<ul>
<li>
Existing user data is updated
</li>
<li>
New user is created with profile received from LDAP-server.
</li>
</ul>
If the password was incorrect:
<ul>
<li>Wrong password error is shown.</li>
</ul>
Features
<ol>
<li>Update user data</li>
<li>Updates user password</li>
<li>Checks password hash using crypt/standart-des, crypt/enhanced, crypt/md5, crypt/blowfish, ssha, smd5, sha, md5</li>
</ol>

WP-LDAP vs LDAP Authentication 2