Datawiza

<p>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.</p>
<p>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>.</p>
<p>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>.</p>
<p>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>.</p>
<p>If you decide to use your own reverse proxy, please follow the instructions below.</p>
<p><strong>How it works</strong></p>
<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>
<p>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:</p>
<p>{<br />
    “role”: “administrator”,<br />
    “email”: “admin@yourwebsite.com”<br />
}</p>
</li>
</ul>
<p><strong>Plugin config in WordPress</strong></p>
<p>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>.</p>
<p><strong>!!! NOTES !!!</strong></p>
<ul>
<li><strong>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.</strong></li>
<li><strong>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.</strong></li>
<li><strong>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.</strong></li>
<li><strong>If admin doesn’t assign role to the user, user’s role will be subscriber for WordPress by default.</strong></li>
<li><strong>If user’s role has been updated in JWT, the plugin will update the role in WordPress accordingly.</strong></li>
</ul>
<p><strong>Generate the JWT required by the plugin</strong></p>
<p>If you are using openresty/lua-nginx-module, here is the code sample to generate the JWT required by the plugin:</p>
<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>
<p>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>.</p>


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 …

jfwenisch

<p>Keystone OIDC transforms your WordPress installation into a fully-featured <strong>OpenID Connect (OIDC) identity provider</strong>, allowing other applications to authenticate users via your WordPress user database.</p>
<h4>Key Features</h4>
<ul>
<li><strong>OIDC Authorization Code Flow</strong> with PKCE support</li>
<li><strong>RS256 JWT</strong> signed access tokens and ID tokens</li>
<li><strong>Admin UI</strong> to create and manage multiple OIDC clients</li>
<li><strong>Client secret management</strong> – generate and reset secrets securely (shown only once)</li>
<li><strong>OIDC Discovery</strong> endpoint (<code>/wenisch-tech/keystone-oidc/.well-known/openid-configuration</code>) for automatic client configuration</li>
<li><strong>Standard scopes</strong>: <code>openid</code>, <code>profile</code>, <code>email</code></li>
<li><strong>Refresh tokens</strong> for long-lived sessions</li>
<li><strong>Zero additional configuration</strong> after install – just create a client and you’re ready</li>
</ul>
<h4>Quick Start</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Go to <strong>OIDC Provider <span aria-hidden="true" class="wp-exclude-emoji">→</span> Add Client</strong> in your WordPress admin</li>
<li>Enter your application name and redirect URI(s)</li>
<li>Copy the generated <strong>Client ID</strong> and <strong>Client Secret</strong> (shown once)</li>
<li>Configure your OIDC client application with the discovery URL shown in the settings</li>
</ol>
<h4>Endpoints</h4>
<p>All URLs are relative to your WordPress site root.</p>
<ul>
<li><strong>Discovery:</strong> <code>/wenisch-tech/keystone-oidc/.well-known/openid-configuration</code></li>
<li><strong>Authorization:</strong> <code>/wenisch-tech/keystone-oidc/oauth/authorize</code></li>
<li><strong>Token:</strong> <code>/wenisch-tech/keystone-oidc/oauth/token</code></li>
<li><strong>UserInfo:</strong> <code>/wenisch-tech/keystone-oidc/oauth/userinfo</code></li>
<li><strong>JWKS:</strong> <code>/wenisch-tech/keystone-oidc/oauth/jwks</code></li>
</ul>
<p>Compatibility aliases are also routed under <code>/wenisch-tech/keystone-oidc/protocol/openid-connect/*</code> for clients that still derive Keycloak-style paths from the custom issuer URI. These aliases are not advertised in discovery.</p>
<h4>UserInfo Example</h4>
<p>For <code>openid profile email</code>, <code>/wenisch-tech/keystone-oidc/oauth/userinfo</code> returns:</p>
<pre><code>{
  "sub": "42",
  "name": "Jane Doe",
  "given_name": "Jane",
  "family_name": "Doe",
  "preferred_username": "jane",
  "email": "jane@example.com",
  "email_verified": true
}

sub is the WordPress user ID as a string, `preferred_username` is the WordPress `user_login`, and `email` is the WordPress `user_email`.
</code></pre>
<p>Roles are not currently emitted. The plugin does not expose WordPress roles or capabilities in UserInfo or ID tokens.</p>
<h3>[2.3.0](https://github.com/wenisch-tech/wordpress-keystone-oidc/compare/v2.2.2…v2.3.0) (2026-06-14)</h3>
<h3>Features</h3>
<ul>
<li>consent-screen now uses theme default colors if available (<a href="https://github.com/wenisch-tech/wordpress-keystone-oidc/commit/24beefead5ac2fab30e0945c58af3f009a733c1c" rel="nofollow ugc">24beefe</a>)</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
<li>ensure compability with wordpress v7 (<a href="https://github.com/wenisch-tech/wordpress-keystone-oidc/commit/36f0d5040ee72d8f2ad9b76ff07da25ed5649bce" rel="nofollow ugc">36f0d50</a>)</li>
</ul>
<h4>2.2.2</h4>
<p>Released on 2026-06-12.</p>
<h4>Bug Fixes</h4>
<ul>
<li>updated release versioning and changelog creation (<a href="https://github.com/wenisch-tech/wordpress-keystone-oidc/commit/98cfb3062232f96346646f915a90198f69b17f51" rel="nofollow ugc">98cfb30</a>)</li>
<li>updated repository links (<a href="https://github.com/wenisch-tech/wordpress-keystone-oidc/commit/f46b2b6f2012cd348eab5e73f5ca9410f0efc406" rel="nofollow ugc">f46b2b6</a>)</li>
<li>updatet generation of changelog. (<a href="https://github.com/wenisch-tech/wordpress-keystone-oidc/commit/357bded5f6cd824859dfc4710d72bdbec60da983" rel="nofollow ugc">357bded</a>)</li>
</ul>
<h4>Documentation</h4>
<ul>
<li>added “Report a bug” button to plugin page (<a href="https://github.com/wenisch-tech/wordpress-keystone-oidc/commit/8281f6c5cfd9474e785c06eaf562e1a2cb84f47d" rel="nofollow ugc">8281f6c</a>)</li>
</ul>
<h4>1.0.0</h4>
<ul>
<li>Initial release</li>
<li>Authorization Code Flow with PKCE</li>
<li>RS256 JWT tokens</li>
<li>Multi-client admin UI with secret management</li>
<li>OIDC Discovery endpoint</li>
<li>Refresh token support</li>
</ul>


Keystone OIDC

Turn your WordPress site into an OpenID Connect (OIDC) identity provider. Manage clients through a simple admin panel.

Datawiza Proxy Auth Plugin – SSO vs Keystone OIDC