cuve

With this plugin, you can ask users to authenticate before they can see your WordPress site. 
You can either use the WordPress logins to authenticate, or a given password. 
This plugin can be useful when your website is still under construction or in beta fase. 
No HTTP Authentication is used.

Basic Authentication

With this plugin, you can ask users to authenticate before they can see your Wordpress site.

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.

Basic Authentication vs Simple LDAP Login