dreitierci

schakko

dreitier

tobi823

FatSquirrel

neosit

medan123

<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.1</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.

apokalyptik

Stephane Daury (stephdau)

Paul Gilzow

<p>Please see the Changelog (Development tab above) for recent updates/changes.</p>
<p>wpDirAuth shifts authentication from the local WordPress instance to a central directory (LDAP) server(s).</p>
<p>wpDirAuth allows users of central directory (LDAP) servers to login to authorized WordPress instances without having to register. The plugin creates a new account for each directory user on first login so that they have full access to preferences and functions, as any WP user would. Activating the plugin will not restrict you to using directory authentication and you will still be able to both create new WP-only users as well as turn on public registration in WordPress. You can also assign any privilege levels to your directory users, and the those users will be referred to their institutional password policy whenever they would normally able to update their WP passwords (on the profile screen, in user edit, etc).</p>
<h4>LDAP/LDAPS</h4>
<p>Authentication should work with most LDAP enabled directory services, such as OpenLDAP, Apache Directory, Microsoft Active Directory, Novell eDirectory, Sun Java System Directory Server, and more. wpDirAuth supports LDAP and LDAPS (SSL) connectivity and can force SSL for WordPress authentication if it is available on the Web server. It also supports server connection pools, for pseudo load balancing and fault tolerance, or multiple source directory authentication. Because the key used to locate a user’s profile in the LDAP server is not always the same, depending on your LDAP server type and institutional choices, you can define your own through the wpDirAuth administration tool. When logging in as a directory user, the WP “remember me” feature is downgraded from 6 months for regular WP users to only 1 hour, so that institutional passwords are not overly endangered when accessing WP from public terminals.</p>
<h4>Branding & Notifications</h4>
<p>You can define notifications addressed to your directory users in key WordPress areas, such as the login screen and the profile edit screen. Since these admin-editable values support HTML (admin, coders, beware of xss!), you can point your directory users to central support information related to functions such as changing their institutional password, a WordPress usage related policy, etc. There is also a simple and optional terms of services concept, only implemented for directory users, which will simply record a one-time acceptance date when agreed upon. Note that agreeing to the TOS has no effect on the user’s level of access in the system, fact which could change in future version if there is a demand for it, or through direct code contribution to that effect.</p>
<h3>Using wpDirAuth</h3>
<p>Once installed and activated, you will be able to administer your directory settings through the dedicated plugin configuration tool found under the <code>wpDirAuth</code> menu found in the WordPress <code>Settings</code> admin section. Directory Authenticated users can now be pre-added to your wordpress system and granted roles by going to the <code>Add Dir Auth User</code> menu found in the WordPress <code>Users</code> admin section. Contextual help for this section is available for this section within WordPress’ built-in help menu. See the inline help found in the tool for more information on the settings. There is a secondary activation toggle, so you can install and activate the plugin, check out the options panel, but not immediately accept directory authentication, or even simply turn the feature on or off at any time.</p>
<h3>Help and Support</h3>
<p>Please post questions, request for help to the WordPress plugins forum or email <a href="mailto:wpdirauth@gilzow.com" rel="nofollow ugc">wpdirauth@gilzow.com</a>. Please be sure to include ‘wpdirauth’ in the subject line.</p>
<h3>TO-DO’s</h3>
<ul>
<li>Internationalization</li>
<li>Refactor to a class</li>
<li>More action/filter hooks</li>
</ul>
<h3>Source and Development</h3>
<p>wpDirAuth welcomes friendly contributors wanting to lend a hand, be it in the form of code through SVN patches, user support, platform portability testing, security consulting, localization help, etc. The [current] goal is to keep the plugin self-contained (ie: no 3rd-party lib) for easier security maintenance, while keeping the code clean and extensible. Focus is on security, features, security, and let’s not forget, security. Unit tests will hopefully be developed and constant security audit performed. Recurring quality patch contributions will lead to commit privileges to the project source repository. Please post questions/requests for help to the wordpress forums and/or email <a href="mailto:wpdirauth@gilzow.com" rel="nofollow ugc">wpdirauth@gilzow.com</a></p>
<h3>License</h3>
<p><a href="http://www.gnu.org/licenses/gpl.html" rel="nofollow ugc">General Public License</a><br />
Copyrights are listed in chronological order, by contributions.<br />
wpDirAuth: WordPress Directory Authentication, original author<br />
Copyright (c) 2007 Stephane Daury – http://stephane.daury.org/<br />
wpDirAuth and wpLDAP Patch Contributions<br />
Copyright (c) 2007 PKR Internet, LLC – http://www.pkrinternet.com/</p>
<p>wpDirAuth Patch Contributions<br />
Copyright (c) 2007 Todd Beverly<br />
wpLDAP: WordPress LDAP Authentication<br />
Copyright (c) 2007 Ashay Suresh Manjure – http://ashay.org/<br />
wpDirAuth Patch Contribution and current maintainer<br />
Copyright (c) 2010-2017 Paul Gilzow – http://gilzow.com/<br />
wpDirAuth is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.<br />
wpDirAuth is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br />
You should have received a copy of the GNU General Public License along with this program. If not, see <a href="http://www.gnu.org/licenses/" rel="nofollow ugc">http://www.gnu.org/licenses/</a>.</p>
<h3>Project History</h3>
<p>Originally started from a patched version of wpLDAP (1.02+patch), wpDirAuth has<br />
since then been heavily overhauled and features have been modified and added.<br />
In other words, a classic case of <code>pimp my lib'</code> (hopefully for the better).<br />
* Current: wpDirAuth: <a href="http://wpdirauth.gilzow.com/" rel="nofollow ugc">http://wpdirauth.gilzow.com/</a><br />
* Original: wpLDAP: <a href="https://wordpress.org/plugins/wpldap/" rel="ugc">https://wordpress.org/plugins/wpldap/</a><br />
* wpLDAP Patch: <a href="https://web.archive.org/web/20100731020249/http://www.pkrinternet.com/~rbulling/private/wpLDAP-1.02-ssl.patch" rel="nofollow ugc">https://web.archive.org/web/20100731020249/http://www.pkrinternet.com/~rbulling/private/wpLDAP-1.02-ssl.patch</a></p>


wpDirAuth

WordPress directory authentication plugin through LDAP and LDAPS (SSL).

Next Active Directory Integration vs wpDirAuth