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

andrewheberle

This plugin allows sign in to WordPress using a JSON Web Token (JWT) contained in a HTTP Header that is added by a reverse proxy 
that sits in front of your WordPress deployment.
Authentication and optionally role assignment is handled by claims contained in the JWT.
Verification of the JWT is handled by either:
<ul>
<li>a shared secret key</li>
<li>retrieving a JSON Web Key Set (JWKS) from a configured URL</li>
</ul>
During the login process if the user does not exist an account will be created with a matching role from the JWT.
If the JWT did not contain a role claim then user is created with the role set in the plugin settings (by default this is the subscriber role).

AH JWT Auth

This plugin allows sign in to WordPress using a JSON Web Token (JWT) contained in a HTTP Header.

Site PIN vs AH JWT Auth