Prashant Baldha

Frontend HTTP Authentication Protection provides simple HTTP authentication layer to your fronend site. There is often need to prevent normal visitors and search engine from navigating front website, when website is in development environment before release website in production environment. This plugin serves this need very well by adding HTTP authentication layer to frontend site. This WordPress Plugin uses HTTP Basic Authentication. This plugin is fully configurable from admin panel.
<h3>Arbitrary section</h3>
Features: 
1.Enable Disable Frontend HTTP Authentication 
2.Set Custom Username and Password 
3.Set Login Message which will display in login dialog prompt 
4.Set error content by WYSWYG editor

Frontend HTTP Auth Protection

Frontend HTTP Authentication Protection makes private front part of your website. When web developer like to give demo of website to end client before …

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

Frontend HTTP Auth Protection vs Site PIN