Datawiza

The Proxy Auth Plugin helps developers/DevOps/admins easily implement authentication and authorization for WordPress by using a <a href="https://en.wikipedia.org/wiki/JSON_Web_Token" rel="nofollow ugc">JWT (JSON Web Token)</a> provided by a reverse proxy.
This could be employed to achieve SSO (OAUTH/OIDC and SAML) to a Cloud Identity Provider (e.g., Azure Active Directory, Okta, Auth0) by using an Identity-Aware Proxy, e.g., <a href="https://www.datawiza.com/" rel="nofollow ugc">Datawiza Access Broker</a> and <a href="https://cloud.google.com/iap" rel="nofollow ugc">Google IAP</a>.
Note that the plugin requires a reverse proxy sitting in front of the WordPress site. The reverse proxy performs authentication, and passes the user name and role in a JWT to the plugin via a HTTP header called <code>DW-TOKEN</code>.
By using <a href="https://www.datawiza.com/" rel="nofollow ugc">Datawiza Access Broker</a>, you get a <a href="https://docs.datawiza.com/step-by-step/step1.html" rel="nofollow ugc">configuration-based</a> <a href="https://docs.datawiza.com/" rel="nofollow ugc">no-code solution</a>, following the detail instruction <a href="https://docs.datawiza.com/step-by-step/step1.html" rel="nofollow ugc">here</a>.
If you decide to use your own reverse proxy, please follow the instructions below.
How it works
<ul>
<li>The plugin retrieves the user id (email) from the JWT and then checks if such a user exists. If not, the plugin creates a new user by using this email and signs him/her in.</li>
<li>The plugin retrieves the user role from the JWT and sets it as the user’s role in WordPress.</li>
<li>
The plugin expects the JWT including user id and role as a HTTP header <code>DW-TOKEN</code>. For example, the payload of JWT may look like:
{ 
 “role”: “administrator”, 
 “email”: “admin@yourwebsite.com” 
}
</li>
</ul>
Plugin config in WordPress
In <code>Setting</code> -> <code>Datawiza Proxy Auth</code>, you need to input a private secret which is used as a Cryptography Key. Such secret is shared between the plugin and the reverse proxy which is responsible for passing the JWT to the plugin. The Signing Algorithm for the JWT is <code>HS256</code>.
!!! NOTES !!!
<ul>
<li>If the enabled Proxy Auth Plugin cannot retrieve the expected JWT in the HTTP header, the plugin will not work. The authentication will use the default authentication of wordpress and you will see an error banner on top of the wordpress pages.</li>
<li>MAKE SURE that clients cannot bypass the reverse proxy. This is to prevent people from sending forged malicious requests with arbitrary JWTs directly to WordPress.</li>
<li>It’s recommended that the reverse proxy in front of the WordPress site erases the incoming http request’s <code>DW-TOKEN</code> header. The <code>DW-TOKEN</code> header should be generated by the reverse proxy only.</li>
<li>If admin doesn’t assign role to the user, user’s role will be subscriber for WordPress by default.</li>
<li>If user’s role has been updated in JWT, the plugin will update the role in WordPress accordingly.</li>
</ul>
Generate the JWT required by the plugin
If you are using openresty/lua-nginx-module, here is the code sample to generate the JWT required by the plugin:
<pre><code>jwt = require("resty.jwt")
local jwt_token = jwt:sign(
 "jwt_secret",
 {
 header={typ="JWT", alg="HS256"},
 payload={email="admin@yourwebsite.com", role="administrator"}
 })
ngx.req.set_header('DW-TOKEN', jwt_token)
</code></pre>
The <code>jwt_secret</code> above should be the same private secret input in <code>Setting</code> -> <code>Datawiza Proxy Auth</code>. The <code>role</code> in <code>payload</code> is optional. If it’s not specified, the default role is <code>subscriber</code>. For more details about <code>lua-resty-jwt</code>, you can visit <a href="https://github.com/SkyLothar/lua-resty-jwt" rel="nofollow ugc">here</a>.

Datawiza Proxy Auth Plugin – SSO

The Proxy Auth Plugin helps developers/DevOps/admins easily implement authentication and authorization for WordPress by using a JWT (JSON Web Token) p …

Automattic

WordPress.org

Alex Kirk

Ashish Kumar (Ashfame)

Paulo Pinto

With this plugin you can use your own WordPress install to authenticate with a webservice that provides <a href="https://openid.net/connect/" rel="nofollow ugc">OpenID Connect</a> to implement Single-Sign On (SSO) for your users.
The plugin is currently only configured using constants and hooks as follows:
<h3>Define the RSA keys</h3>
If you don’t have keys that you want to use yet, generate them using these commands:
<pre><code>openssl genrsa -out oidc.key 4096
openssl rsa -in oidc.key -pubout -out public.key
</code></pre>
And make them available to the plugin as follows (this needs to be added before WordPress loads):
<pre><code>define( 'OIDC_PUBLIC_KEY', <<<OIDC_PUBLIC_KEY
-----BEGIN PUBLIC KEY-----
...
-----END PUBLIC KEY-----
OIDC_PUBLIC_KEY
);

define( 'OIDC_PRIVATE_KEY', <<<OIDC_PRIVATE_KEY
-----BEGIN PRIVATE KEY-----
...
-----END PRIVATE KEY-----
OIDC_PRIVATE_KEY
);
</code></pre>
Alternatively, you can also put them outside the webroot and load them from the files like this:
<pre><code>define( 'OIDC_PUBLIC_KEY', file_get_contents( '/web-inaccessible/oidc.key' ) );
define( 'OIDC_PRIVATE_KEY', file_get_contents( '/web-inaccessible/private.key' ) );
</code></pre>
<h3>Define the clients</h3>
Define your clients by adding a filter to <code>oidc_registered_clients</code> in a separate plugin file or <code>functions.php</code> of your theme or in a MU-plugin like:
<pre><code>add_filter( 'oidc_registered_clients', 'my_oidc_clients' );
function my_oidc_clients() {
 return array(
 'client_id_random_string' => array(
 'name' => 'The name of the Client',
 'secret' => 'a secret string',
 'redirect_uri' => 'https://example.com/redirect.uri',
 'grant_types' => array( 'authorization_code' ),
 'scope' => 'openid profile',
 ),
 );
}
</code></pre>
<h3>Exclude URL from caching</h3>
<ul>
<li><code>example.com/wp-json/openid-connect/userinfo</code>: We implement caching exclusion measures for this endpoint by setting <code>Cache-Control: 'no-cache'</code> headers and defining the <code>DONOTCACHEPAGE</code> constant. If you have a unique caching configuration, please ensure that you manually exclude this URL from caching.</li>
</ul>
<h3>Github Repo</h3>
You can report any issues you encounter directly on <a href="https://github.com/Automattic/wp-openid-connect-server" rel="nofollow ugc">Github repo: Automattic/wp-openid-connect-server</a>

OpenID Connect Server

Use OpenID Connect to log in to other webservices using your own WordPress.

Datawiza Proxy Auth Plugin – SSO vs OpenID Connect Server