meritstory

karolismerit

Microsoft Login for WordPress 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.
<h4>Why this plugin?</h4>
<ul>
<li>Microsoft-focused. Built specifically for Azure AD / Entra ID.</li>
<li>Simple setup. Import SAML metadata or use OIDC discovery to auto-fill endpoints.</li>
<li>Clean admin UX. One settings area with guided setup and test tools.</li>
<li>Security-first. 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>
SAML:
<ol>
<li>Install and activate the plugin.</li>
<li>Go to Settings -> SSO & SAML Login.</li>
<li>Copy the SP Entity ID and ACS URL 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 App Federation Metadata URL into the plugin and click Import Metadata.</li>
<li>Save settings. Your Microsoft login button appears on <code>wp-login.php</code>.</li>
</ol>
OIDC:
<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 OpenID Connect, enter Tenant ID, click Fetch Discovery.</li>
<li>Enter Client ID and Client Secret, then save.</li>
</ol>
<h4>Privacy</h4>
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.
<h3>External services</h3>
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.
1) Microsoft Azure AD / Entra ID (required for SSO login)
Used for SAML 2.0 and OpenID Connect authentication.
Data sent and when:
<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>
Returned identity claims (email, name, subject/object ID, roles/groups) are used to authenticate/provision users and stored in your WordPress database.
<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>
2) Microsoft Graph API (Pro only; when configured by the site admin)
Used to sync users and groups from Microsoft Entra ID into WordPress.
Data sent and when:
<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>
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.
<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>
3) Freemius (optional; only when admin opts in or activates a paid license)
Used for licensing, upgrade flow, and optional analytics.
Data sent and when:
<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>
If telemetry opt-in is accepted, usage and diagnostic events may be sent per Freemius configuration.
</li>
<li>
Service: https://freemius.com/
</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.

vivokey

VivoKey is a digital identity platform that links your online digital identity VivoKey profile with one or more implantable cryptobionic NFC transponders. This plugin will enable you to use your VivoKey digial identity profile to authetnicate your WordPress account by scanning your VivoKey cryptobionic implant, rather than enter your username and password. The plugin utilizes VivoKey’s web-standard OpenID Connect API. Details about the API can be found at <a href="https://vivokey.com/api" rel="nofollow ugc">https://vivokey.com/api</a>
Check out this video that details how to configure and use the VivoKey OpenID Connect plugin for WordPress:
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/N30D9uImIxA?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
To see a list of available VivoKey plugins, please check here: <a href="https://vivokey.com/plugins" rel="nofollow ugc">https://vivokey.com/plugins</a>
<h3>Contribute</h3>
Please feel free to clean up the code, add features and fix bugs. The current code serves only as a basic implementation with many potential improvements.
<a href="https://github.com/VivoKey/plugin-wordpress" rel="nofollow ugc">https://github.com/VivoKey/plugin-wordpress</a>
Pull requests welcome.

VivoKey OpenID Connect

Authenticate your WordPress account by scanning your VivoKey cryptobionic implant instead of using your username and password.

SSO & SAML Login — Azure AD / Entra ID vs VivoKey OpenID Connect