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

256hax

Attackers trying to breakthrough WordPress admin page. Basic Authentication helps to prevent attacks. 
But some case it can’t modify .htaccess or ssl.conf.
This plugin is useful for servers where prohibition modify Apache conf(.htaccess) or Nginx conf(ssl.conf). 
Protect WordPress admin page on similar Basic Auth. It doesn’t need .htaccess or ssl.conf.
<h4>Features</h4>
<ul>
<li>Auth log in with User Name and Password.</li>
<li>Customization title and message in Login page.</li>
</ul>
<h4>Note</h4>
This plugin doesn’t replace Basic Authentication. If you can modify .htaccess or ssl.conf, I recommend using that. See differences running layer.
<h4>Running Layer</h4>
Fronts-end (ex: CSS, Javascript) 
Application Plugin <- This plugin 
Application (ex: WordPress) 
Programming language (ex: PHP) 
Middleware Web (ex: Apache, Nginx) <- .htaccess Basic Authentication 
Middleware DB / OS

WP Similar Basic Auth

Protect WordPress admin page on similar Basic Auth without .htaccess.

Site PIN vs WP Similar Basic Auth