Aaron Axelsen

<p>LDAP authentication is configured on a site-wide (as opposed to per-blog) level, so only Network Admin accounts have access to the configuration to LDAP connection information.</p>
<p>Please make sure you have PHP compiled with LDAP support.  This will show up as an LDAP section in your phpinfo() if it is correct.</p>
<p>Remember – all the code for the plugin was contributed by volunteers, and you can show your gratitude by giving back to the community!</p>
<h3>How It Works</h3>
<p>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<br />
algorithm:</p>
<p>Create a new WPMU User, with LDAP username and a randomly generated password.<br />
Some user information, such as first and last name, is extracted from the<br />
  information returned from the LDAP server.<br />
Actions for user creation and activation are triggered.<br />
The user’s domain / URL are created depending on plugin configuration (i.e.,<br />
  VHost vs SubDir).<br />
If the option is set, a blog is created, with path and name based on the LDAP<br />
  username and the blog is activated with the user being Administrator, and<br />
  appropriate actions are triggered.</p>
<p>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.</p>


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 …

dreitierci

schakko

dreitier

tobi823

medan123

neosit

FatSquirrel

<p><em>Next Active Directory Integration</em> allows WordPress to authenticate, authorize, create and update users against Microsoft Active Directory. <em>NADI</em> ist a complete rewrite of its predecessor Active Directory Integration and therefore an own plugin.<br />
You can easily import users from your Active Directory into your WordPress instance and keep both synchronized through <em>Next Active Directory Integration’s</em> features.</p>
<p>Even if <em>NADI</em> is available for free we hope you purchase a plan to let us continue the work on Next Active Directory Integration.<br />
You can purchase commercial support plans at <a href="https://www.active-directory-wp.com/shop-overview/" rel="nofollow ugc">https://www.active-directory-wp.com/shop-overview/</a>. The support plans give you access to our premium extensions and guarantee an ongoing development of the plug-in.</p>
<h4>Features</h4>
<ul>
<li>Authenticating WordPress users against one or multiple AD Server</li>
<li>Authorizing users by Active Directory group memberships</li>
<li>Managing Active Directory authentication for WordPress Multisite installations</li>
<li>Single Sign On with Kerberos sponsored by <a href="http://colt.net" rel="nofollow ugc">Colt Technology Services</a> and <a href="https://app.digitalelite.co.uk/" rel="nofollow ugc">Digital Elite</a></li>
<li>Automatically create and update WordPress users based upon their Active Directory membership</li>
<li>Mapping of Active Directory security groups to WordPress roles</li>
<li>Protection against brute force password hacking attacks</li>
<li>User and/or admin e-mail notification on failed login attempts</li>
<li>Multi-language support (at the moment only English is included)</li>
<li>Determining WordPress display name from Active Directory attributes</li>
<li>Synchronizing Active Directory attributes and WordPress user meta information in both ways</li>
<li>Embed customized Active Directory attributes in WordPress user’s profile</li>
<li>Enable/disable password changes for local (non-Active Directory) WordPress users</li>
<li>Disable user accounts in WordPress if they are disabled in Active Directory.</li>
<li>Set users local WordPress password on first and/or on every successful login</li>
<li>Option to disable fallback to local (WordPress) authentication.</li>
<li>Support for Active Directory forest environments.</li>
<li>and much much more</li>
</ul>
<h4>Premium Extensions</h4>
<p>As an owner of a valid support plan you have access to the following premium extensions:</p>
<ul>
<li>Profile Pictures: Synchronize profile photos from Active Directory to WordPress without a 3rd party plug-in</li>
<li>BuddyPress profile photo: Synchronize profile photos from Active Directory to BuddyPress</li>
<li>Buddy Press simple attributes: Synchronize attributes from Active Directory/NADI to BuddyPress’ custom profiles</li>
<li>Login with Ultimate Member: Let UM users log in by using NADI</li>
<li>Login with WooCommerce: Let WooCommerce users log in by using NADI</li>
<li>WP-CLI: Execute common NADI tasks (Sync to WordPress, Sync to AD) with help of WP-CLI</li>
<li>Active Directory Forest: Be able to use one WordPress instance with your whole Active Directory forest environment</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress since 5.6</li>
<li>PHP >= 8.2</li>
<li>LDAP support</li>
<li>OpenSSL Support for TLS (recommended)</li>
</ul>


Next Active Directory Integration

I had some issues finding out how to configure it correctly. I usually login with "INTERN\john.doe", but a format like this was not valid. I found out that I had to use "john.doe@intern.example.com" and to add the two suffixes "@intern.example.com" as well as "@example.com". I activated the automatic user creation and all worked easily. Awesome work!

Once you figure out your configuration, it work perfectly!

Next Active Directory Integration allows WordPress to authenticate, authorize, create and update users against Microsoft Active Directory.

WPMU Ldap Authentication vs Next Active Directory Integration