Daniel Bachhuber

Chris Reynolds

John Spellman

Pantheon Systems

Josh Koenig

Anais Pantheor

<p>SAML authentication for WordPress, using the bundled OneLogin SAML library or optionally installed <a href="https://simplesamlphp.org/" rel="nofollow ugc">SimpleSAMLphp</a>. OneLogin provides a SAML authentication bridge; SimpleSAMLphp provides SAML plus a variety of other authentication mechanisms. This plugin acts as a bridge between WordPress and the authentication library.</p>
<p>If your organization uses Google Apps, <a href="https://pantheon.io/docs/wordpress-google-sso/" rel="nofollow ugc">integrating Google Apps with WP SAML Auth</a> takes just a few steps.</p>
<p>The standard user flow looks like this:</p>
<ul>
<li>User can log in via SAML using a button added to the standard WordPress login view.</li>
<li>When the button is clicked, the user is handed off to the authentication library. With OneLogin, the user is redirected to the SAML identity provider. With SimpleSAMLphp, the user is redirected to the SimpleSAMLphp install.</li>
<li>Once the user is authenticated with the identity provider, they’re redirected back to WordPress and signed in to their account. A new WordPress user will be created if none exists (although this behavior can be disabled).</li>
<li>When the user logs out of WordPress, they are also logged out of the identity provider.</li>
</ul>
<p>A set of configuration options allow you to change the plugin’s default behavior. For instance, <code>permit_wp_login=>false</code> will force all authentication to go through the SAML identity provider, bypassing <code>wp-login.php</code>. Similiarly, <code>auto_provision=>false</code> will disable automatic creation of new WordPress users.</p>
<p>See installation instructions for full configuration details.</p>
<h3>Installing SimpleSAMLphp</h3>
<p>The plugin supports both SimpleSAMLphp v1.x and v2.x. The autoloader is automatically detected:</p>
<p><strong>SimpleSAMLphp v2.x</strong> uses <code>vendor/autoload.php</code><br />
<strong>SimpleSAMLphp v1.x</strong> uses <code>lib/_autoload.php</code></p>
<h4>Default Search Paths</h4>
<p>The plugin automatically searches for SimpleSAMLphp in these locations:<br />
* <code>ABSPATH . 'simplesaml'</code><br />
* <code>ABSPATH . 'private/simplesamlphp'</code><br />
* <code>ABSPATH . 'simplesamlphp'</code><br />
* <code>ABSPATH . 'vendor/simplesamlphp/simplesamlphp'</code> (Composer installation)<br />
* <code>plugin_dir_path . 'simplesamlphp'</code></p>
<p>For each path, the plugin checks for both <code>vendor/autoload.php</code> (v2.x) and <code>lib/_autoload.php</code> (v1.x).</p>
<p><strong>This means Composer installations work automatically!</strong> If you run <code>composer require simplesamlphp/simplesamlphp</code> in your site root, the plugin will find it without any additional configuration.</p>
<h4>Composer Installation (Advanced)</h4>
<p>If you install SimpleSAMLphp via Composer to a <strong>custom location</strong> (not the standard <code>vendor/simplesamlphp/simplesamlphp</code>), you can specify the autoloader path:</p>
<pre><code>add_filter( 'wp_saml_auth_option', function( $value, $option_name ) {
    if ( 'simplesamlphp_autoload' === $option_name ) {
        // Point to your custom Composer vendor autoloader
        return '/custom/path/vendor/autoload.php';
    }
    return $value;
}, 10, 2 );
</code></pre>
<h4>Custom Installation Paths</h4>
<p>If SimpleSAMLphp is installed in a non-default location, you can set custom search paths with the <code>wp_saml_auth_simplesamlphp_path_array</code> filter:</p>
<pre><code>add_filter( 'wp_saml_auth_simplesamlphp_path_array', function( $simplesamlphp_path_array ) {
    // Override default paths with custom paths
    return [ '/custom/path/to/simplesamlphp' ];
} );
</code></pre>
<p>Or define an explicit autoloader path with the <code>wp_saml_auth_ssp_autoloader</code> filter:</p>
<pre><code>add_filter( 'wp_saml_auth_ssp_autoloader', function( $ssp_autoloader ) {
    return ABSPATH . 'path/to/simplesamlphp/vendor/autoload.php';
} );<h3>WP-CLI Commands</h3>
</code></pre>
<p>This plugin implements a variety of <a href="https://wp-cli.org" rel="nofollow ugc">WP-CLI</a> commands. All commands are grouped into the <code>wp saml-auth</code> namespace.</p>
<pre><code>$ wp help saml-auth

NAME

  wp saml-auth

DESCRIPTION

  Configure and manage the WP SAML Auth plugin.

SYNOPSIS

  wp saml-auth <command>

SUBCOMMANDS

  scaffold-config      Scaffold a configuration filter to customize WP SAML Auth usage.
</code></pre>
<p>Use <code>wp help saml-auth <command></code> to learn more about each command.</p>
<p><strong>Note:</strong> The <code>scaffold-config</code> command generates a configuration function with default values. The <code>simplesamlphp_autoload</code> option is not included in the scaffolded output because the plugin auto-detects SimpleSAMLphp installations. Only add this option manually if SimpleSAMLphp is in a non-standard location.</p>
<h3>Contributing</h3>
<p>See <a href="https://github.com/pantheon-systems/wp-saml-auth/blob/main/CONTRIBUTING.md" rel="nofollow ugc">CONTRIBUTING.md</a> for information on contributing.</p>


WP SAML Auth

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.

WP SAML Auth vs SSO & SAML Login — Azure AD / Entra ID