Marcus Downing

Dani Llewellyn

Whenever a site is under development, or its content should remain private, you want to prevent to general public 
from reading it – whether deliberately or by accident.
A comman way to do this is with <a href="http://httpd.apache.org/docs/2.4/howto/auth.html" rel="nofollow ugc">HTTP authorisation</a>, 
but this has some problems:
<ul>
<li>Each user of your site has two different sets of username and password, one for the authorisation and one for 
WordPress login. It’s not uncommon for some users to find this confusing.</li>
<li>To set up authorisation you need access to your web server’s configuration (at least using the <code>.htaccess</code> file), 
which may not be available depending on your hosting supplier. 
You also need to learn how to configure the authorisation correctly, and risk breaking the site if you get it wrong.</li>
<li>When the time comes to remove the authorisation, you need to edit the configuration again.</li>
<li>In certain circumstances, combining authorisation with WordPress login can get a visitor into a circular redirect 
loop, where the result of logging in is to redirect to the login page.</li>
</ul>
Site PIN solves these problems by replacing authorisation with a simple PIN. This has the following advantages:
<ul>
<li>Everybody knows what a PIN is, and it’s clearly not the same as a password.</li>
<li>Logging into WordPress bypasses the PIN, so you can’t lock yourself out</li>
<li>It’s just a WordPress plugin, so no server configuration is necessary.</li>
<li>You can change or remove the PIN from WordPress admin.</li>
</ul>

Site PIN

Prevent careless visitors by locking your site down with a PIN

heiglandreas

Use your existing LDAP as authentication-backend for your wordpress!
So what are the differences to other WordPress-LDAP-Authentication-Plugins?
<ul>
<li>Flexible: You are totaly free in which LDAP-backend to use. Due to the extensive configuration you can freely decide how to do the authentication of your users. It simply depends on your filters</li>
<li>Independent: As soon as a user logs in, it is added/updated to the WordPress’ user-database to allow wordpress to always use the correct data. You only have to administer your users once.</li>
<li>Failsafe: Due to the users being created in WordPress’ User-database they can also log in when the LDAP-backend currently is gone.</li>
<li>Role-Aware: You can map WordPress’ roles to values of an existing LDAP-attribute.</li>
</ul>
For more Information on the configuration have a look at https://github.com/heiglandreas/authLdap

authLdap

This plugin is the only one in WP.org which works out of the box, it's super easy to set up and even has user group mapping included. Thanks once again and totally recommended to every one.

Karolina

Works perfectly and has group mapping!

Use your existing LDAP flexible as authentication backend for WordPress

Site PIN vs authLdap