Meitar

<p>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.</p>
<p><em>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!</em></p>
<p>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:</p>
<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>
<p>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>.</p>
<p>In addition to the above mappings, the following optional mappings also take place if or when the user updates their user profile:</p>
<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>
<p>Moreover, WP-LDAP is aware of certain features provided by other plugins. These include:</p>
<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>
<p>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.<br />
This plugin is free software, but grocery stores do not offer free food. <em>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!</em></p>


WP-LDAP

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

Curtiss Grymala

<p>This plugin allows you to query an active directory server to retrieve an optionally filtered list of users and display it as a list within a WordPress site. Some of the features of this plugin include:</p>
<ul>
<li>Widget – a widget is provided, with a few filtering/formatting options, to allow you to display a user list in any widgetized area</li>
<li>Shortcode – a shortcode is provided, with all of the plugin’s filtering/formatting options, to allow you to display a user list within any page or post</li>
<li>Output builder – a full-featured output builder is provided, allowing you to completely customize the format in which each user is displayed within the list. The output builder even allows conditional (if…elseif…else) statements.</li>
<li>Format options – in addition to the output builder (which is used for each individual user), the following formatting options are also available:
<ul>
<li>before_list – Any HTML code you would like to appear before the list of employees. This code is output before the opening title_wrap tag.</li>
<li>after_list – Any HTML code you would like to appear after the list of employees. This code is output after the closing list_wrap tag.</li>
<li>after_title – Any HTML code you would like to appear between the closing title_wrap tag and the opening list_wrap tag.</li>
<li>title_wrap – The HTML element you would like to use to wrap the list title (if set). Just the element name, please; no opening or closing brackets.</li>
<li>title_class – The CSS class you would like applied to the list title (if set). If you would prefer that no CSS class be applied to the title, leave this blank.</li>
<li>title_id – If you would like to apply an HTML ID to the list title, you can indicate that here. Remember that IDs should be unique, so, if you plan on using multiple employee lists on a single page, you should leave this blank.</li>
<li>title – The title you would like to appear at the top of the list. The title is output prior to the opening of the list itself.</li>
<li>list_wrap – The HTML element you would like to use to wrap the entire list. Just the element name, please; no opening or closing brackets.</li>
<li>list_class – The CSS class you would like to assign to the opening list_wrap tag, aiding in styling the entire list. If you would prefer that no CSS class be applied to the list, leave this blank.</li>
<li>list_id – If you would like to apply an HTML ID to the list itself, you can indicate that here. Remember that IDs should be unique, so, if you plan on using multiple employee lists on a single page, you should leave this blank.</li>
<li>item_wrap – The HTML element you would like to use to wrap each individual employee in the list. Just the element name, please; no opening or closing brackets.</li>
<li>item_class – The CSS class you would like to assign to each individual employee in the list. If you would prefer that no CSS class be applied to the list, leave this blank.</li>
<li>item_id – If you would like to apply an HTML ID to each individual employee in the list, you can indicate that here. You can use placeholder variables for user information (any of the fields that are set to be retrieved, plus the user’s username (samaccountname). Simply wrap the placeholder variable with percent symbols (so, to use a placeholder for samaccountname, use %samaccountname%) All disallowed characters (the @ symbol, dots, spaces, etc.) will be replaced with hyphens. Remember that IDs should be unique, so, if you plan on using multiple employee lists that may include the same employee multiple times on a single page, you should leave this blank. Likewise, you should use a placeholder variable that will be unique.</li>
</ul>
</li>
<li>Field chooser – choose which Active Directory fields to retrieve from the server (note that any fields included in the output builder must be chosen in the field chooser, otherwise they won’t be retrieved and, therefore, won’t be displayed)</li>
<li>Single user display – feed a username to the shortcode or widget, and a single user will be retrieved and displayed, rather than a list of users</li>
<li>Search form – a simple search form (the input keyword is searched against all fields being retrieved) is provided</li>
<li>Multisite-compatible – Options can be set for the entire network, and can be overridden on each individual site within the network. Some options can even be overridden in the widget or shortcode itself.</li>
<li>Information cache – Information retrieved by this plugin is cached for 24 hours after it is retrieved (this option is not currently configurable, but will probably be in future versions) in order to avoid hitting the AD server more than necessary.</li>
</ul>
<p>You can connect to the Active Directory server using SSL and/or TLS, if desired. You can also provide multiple Active Directory server addresses to allow load-balancing (a random server is chosen from the list before connecting and querying).</p>
<h4>Compatibility Note and Credits</h4>
<p>This plugin currently utilizes version 3.3.2 (with some extended functionality built specifically for this plugin) of the <a href="http://adldap.sourceforge.net/" rel="nofollow ugc">adLDAP class</a> from Scott Barnett & Richard Hyland. It has also been tested with version 3.1-Extended and version 3.3.2-Extended as they are included with various versions of the <a href="https://wordpress.org/extend/plugins/active-directory-authentication-integration/" rel="ugc">Active Directory Authentication Integration</a> and <a href="https://wordpress.org/extend/plugins/active-directory-integration/" rel="ugc">Active Directory Integration</a> plugins. This plugin is potentially incompatible (and has not been tested) with Active Directory Integration, though; as it all depends on in which order the adLDAP class is instantiated (if this plugin’s copy of adLDAP is included before that plugin’s version, that plugin may not work properly).</p>
<p>This plugin was developed by <a href="https://wordpress.org/support/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.</p>
<h4>Important Note</h4>
<p>At this time, this plugin has only been tested on a handful of WordPress installations (all on similar server configurations) with a single Active Directory server, so it is entirely possible that there will be bugs or errors that stop it (or other plugins) from working properly. In order to improve this plugin, please share any feedback you have.</p>
<h3>To Do</h3>
<ul>
<li>Implement pagination</li>
<li>Provide a work-around for the PHP “paging” error</li>
<li>Investigate allowing results to be filtered by multiple groups</li>
<li>Investigate allowing results to be filtered by multiple usernames</li>
</ul>


Active Directory Employee Listing

Retrieve lists of active directory users and display them in WordPress.

WP-LDAP vs Active Directory Employee Listing