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.

meritstory

karolismerit

<p><strong>Microsoft Login for WordPress</strong> lets your users sign in to WordPress using their Microsoft Azure AD / Entra ID credentials – no separate password needed. Choose between SAML 2.0 and OpenID Connect (OIDC) to match your organization’s configuration.</p>
<h4>Why this plugin?</h4>
<ul>
<li><strong>Microsoft-focused.</strong> Built specifically for Azure AD / Entra ID.</li>
<li><strong>Simple setup.</strong> Import SAML metadata or use OIDC discovery to auto-fill endpoints.</li>
<li><strong>Clean admin UX.</strong> One settings area with guided setup and test tools.</li>
<li><strong>Security-first.</strong> SAML uses <code>onelogin/php-saml</code>; OIDC validates RS256 tokens against JWKS.</li>
</ul>
<h4>Free Features</h4>
<ul>
<li>SAML 2.0 SP login flow (Azure AD / Entra ID as IdP)</li>
<li>OpenID Connect Authorization Code + PKCE login flow</li>
<li>Auto-create WordPress users on first login (JIT provisioning)</li>
<li>Configurable default role for new users</li>
<li>SP metadata download and SAML metadata URL import</li>
<li>OIDC tenant discovery and endpoint validation tools</li>
<li>Emergency admin bypass URL for lockout recovery</li>
<li>WP-CLI commands (<code>wp saml status</code>, <code>wp saml import-metadata</code>, <code>wp saml regen-cert</code>, <code>wp saml test</code>)</li>
</ul>
<h4>Pro Features (separate plugin)</h4>
<ul>
<li>Role mapping (map Azure AD roles/groups to WordPress roles)</li>
<li>SSO enforcement by WordPress role, with per-user bypass exceptions</li>
<li>Attribute sync on login (first name, last name, display name)</li>
<li>Audit log (login success/failure, user creation, role mapping, SSO enforcement, logout)</li>
<li>Audit log CSV export and retention settings</li>
<li>Microsoft Graph user sync and import tools:</li>
<li>App-only Graph connection test</li>
<li>Group member preview/import</li>
<li>Daily background sync via WP-Cron</li>
<li>Optional deprovisioning (remove role when user is disabled/removed)</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>PHP 8.0 or higher</li>
<li>PHP extensions: <code>openssl</code>, <code>dom</code>, <code>zlib</code></li>
<li>WordPress 6.3 or higher</li>
<li>A Microsoft Azure AD / Entra ID tenant</li>
</ul>
<h4>Setup Overview</h4>
<p><strong>SAML:</strong></p>
<ol>
<li>Install and activate the plugin.</li>
<li>Go to <strong>Settings -> SSO & SAML Login</strong>.</li>
<li>Copy the <strong>SP Entity ID</strong> and <strong>ACS URL</strong> from the SP Information tab.</li>
<li>Create a new Enterprise Application in Azure AD (non-gallery app, enable SAML SSO).</li>
<li>Paste your <strong>App Federation Metadata URL</strong> into the plugin and click <strong>Import Metadata</strong>.</li>
<li>Save settings. Your Microsoft login button appears on <code>wp-login.php</code>.</li>
</ol>
<p><strong>OIDC:</strong></p>
<ol>
<li>Create an App Registration in Azure and add your site’s <code>/saml/oidc-callback</code> as Redirect URI.</li>
<li>In plugin settings, select <strong>OpenID Connect</strong>, enter Tenant ID, click <strong>Fetch Discovery</strong>.</li>
<li>Enter <strong>Client ID</strong> and <strong>Client Secret</strong>, then save.</li>
</ol>
<h4>Privacy</h4>
<p>This plugin does not send data to third parties except as described in the External services section below. SSO and audit data are stored in your own WordPress database.</p>
<h3>External services</h3>
<p>This plugin connects to external services to provide authentication and optional paid features. No data is sent to any external service except as described below.</p>
<p><strong>1) Microsoft Azure AD / Entra ID (required for SSO login)</strong></p>
<p>Used for SAML 2.0 and OpenID Connect authentication.</p>
<p>Data sent and when:</p>
<ul>
<li>On SSO login start, the browser is redirected to Microsoft with Azure app/protocol parameters (tenant endpoint, app/client ID, redirect URI, state, scopes, SAML request/relay state as applicable).</li>
<li>On OIDC callback, the site sends the one-time authorization code (and PKCE verifier) to Microsoft’s token endpoint.</li>
<li>On SAML setup import/test actions, the site fetches your tenant’s federation metadata URL.</li>
<li>On logout (if SLO/end-session is enabled), the browser is redirected to Microsoft’s logout endpoint.</li>
</ul>
<p>Returned identity claims (email, name, subject/object ID, roles/groups) are used to authenticate/provision users and stored in your WordPress database.</p>
<ul>
<li>Service: https://login.microsoftonline.com/</li>
<li>Privacy Policy: https://privacy.microsoft.com/en-us/privacystatement</li>
<li>Terms of Service: https://www.microsoft.com/en-us/servicesagreement</li>
</ul>
<p><strong>2) Microsoft Graph API (Pro only; when configured by the site admin)</strong></p>
<p>Used to sync users and groups from Microsoft Entra ID into WordPress.</p>
<p>Data sent and when:</p>
<ul>
<li>When an admin runs a Graph test, import, or sync (manual or scheduled), the site sends requests to Microsoft Graph using app-only access tokens.</li>
<li>Requests include query parameters for the configured sync operations (group/member lookups, account status checks, etc.).</li>
</ul>
<p>Returned directory fields (user principal name, email, display name, object IDs, group membership, account status) are used to create, update, or deprovision WordPress users per plugin settings.</p>
<ul>
<li>Service: https://graph.microsoft.com/</li>
<li>Privacy Policy: https://privacy.microsoft.com/en-us/privacystatement</li>
<li>Terms of Service: https://www.microsoft.com/en-us/servicesagreement</li>
</ul>
<p><strong>3) Freemius (optional; only when admin opts in or activates a paid license)</strong></p>
<p>Used for licensing, upgrade flow, and optional analytics.</p>
<p>Data sent and when:</p>
<ul>
<li>On activation, an opt-in prompt is shown; no data is sent unless the admin consents.</li>
<li>On license activation/validation, the site exchanges license, account, and site information with Freemius servers.</li>
<li>
<p>If telemetry opt-in is accepted, usage and diagnostic events may be sent per Freemius configuration.</p>
</li>
<li>
<p>Service: https://freemius.com/</p>
</li>
<li>Privacy Policy: https://freemius.com/privacy/</li>
<li>Terms of Service: https://freemius.com/terms/</li>
</ul>


SSO & SAML Login — Azure AD / Entra ID

Log in to WordPress with Microsoft Azure AD / Entra ID using SAML 2.0 or OpenID Connect (OIDC). Simple setup, enterprise-grade security.

Keystone OIDC vs SSO & SAML Login — Azure AD / Entra ID