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 …

markmont

This plugin is for a very specific use case: Your WordPress website is part of an organization that uses OpenID Connect (OIDC) for web single-sign-on as well as for group-based authorization. In that case, this plugin will let you restrict access to parts of your WordPress website based on OIDC login and group membership information.
This plugin has been tested with:
<ul>
<li><a href="https://www.shibboleth.net/" rel="nofollow ugc">Shibboleth</a> OIDC using the <code>edumember_ismemberof</code> attribute for LDAP group membership.</li>
</ul>
Features:
<ul>
<li>Allow site visitors to log in via OIDC without needing a WordPress user account.</li>
<li>Optionally allow WordPress users to log in via OIDC instead of using their WordPress password.</li>
<li>Optionally restrict access to the entire site to logged-in users or only members of specific groups.</li>
<li>Optionally restrict access to specific pages and posts to logged-in users or only members of specific groups.</li>
<li>Show parts of pages/posts/widgets only to logged-in users or members of specific groups.</li>
<li>Access restrictions apply to site visitors, feeds, the REST API, and XMLRPC.</li>
<li>Shortcodes (Gutenberg blocks planned for a future release)
<ul>
<li><code>umich_oidc_button</code> – Generate a login or logout button.</li>
<li><code>umich_oidc_link</code> – Generate a login or logout link.</li>
<li><code>umich_oidc_logged_in</code> – Show content only if the visitor is logged in.</li>
<li><code>umich_oidc_member</code> – Show content only if the visitor is a member of one or more groups.</li>
<li><code>umich_oidc_not_logged_in</code> – Show content only if the visitor is NOT logged in.</li>
<li><code>umich_oidc_not_member</code> – Show content only if the visitor NOT a member of the specified groups.</li>
<li><code>umich_oidc_url</code> – Generate a login or logout URL.</li>
<li><code>umich_oidc_userinfo</code> – Display information about the currently-logged-in OIDC user.</li>
</ul>
</li>
</ul>
<h3>Restricting private content in search results</h3>
You can prevent content from showing up in web search engine results by restricting access to particular pages/posts.
Search results from WordPress’ built-in search will only show content that the searching user has access to.
WARNING: WordPress search plugins may show content that the user does not have access to, leaking private information. Please test search plugins before enabling them. If a search plugin provides an appropriate WordPress hook for limiting search results, contact us, and we may be able to add support for it to UMich OIDC Login.
<h3>Copyright and license information</h3>
Copyright (c) 2022 Regents of the University of Michigan.
This file is part of the UMich OIDC Login WordPress plugin.
UMich OIDC Login is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
UMich OIDC Login is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with UMich OIDC Login. If not, see <a href="https://www.gnu.org/licenses/" rel="nofollow ugc">https://www.gnu.org/licenses/</a>.

UMich OIDC Login

Restrict access to the whole site or only certain parts based on OpenID Connect (OIDC) login and group membership information.

Datawiza Proxy Auth Plugin – SSO vs UMich OIDC Login