markmont

<p>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.</p>
<p>This plugin has been tested with:</p>
<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>
<p>Features:</p>
<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>
<p>You can prevent content from showing up in web search engine results by restricting access to particular pages/posts.</p>
<p>Search results from WordPress’ built-in search will only show content that the searching user has access to.</p>
<p><strong>WARNING:</strong> 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.</p>
<h3>Copyright and license information</h3>
<p>Copyright (c) 2022 Regents of the University of Michigan.</p>
<p>This file is part of the UMich OIDC Login WordPress plugin.</p>
<p>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.</p>
<p>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.</p>
<p>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>.</p>


UMich OIDC Login

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

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.

UMich OIDC Login vs Keystone OIDC