idgold

<p>Open Access SSO is a SAML 2.0 Service Provider for WordPress. It lets users sign in to your site through any standard SAML identity provider (Microsoft Entra ID, Okta, OneLogin, Keycloak, ADFS, Shibboleth, NetIQ Access Manager, etc.) instead of (or alongside) the built-in WordPress login form.</p>
<p>Built from scratch as a clean-room implementation. Fully open-source under GPLv2+. No paid tier, no telemetry. Its only third-party libraries are xmlseclibs (MIT) for XML signature handling and phpseclib (MIT) for RSA-OAEP key unwrapping — both bundled, and neither makes any network call.</p>
<h4>What it does</h4>
<ul>
<li><strong>SAML 2.0 SP</strong> with HTTP-Redirect and HTTP-POST bindings, signed AuthnRequests, signed/encrypted assertion handling, SP-initiated and IdP-initiated Single Logout.</li>
<li><strong>Multi-IdP</strong> — configure multiple identity providers, let users choose via a button or URL parameter (<code>?idp=slug</code>).</li>
<li><strong>Attribute mapping</strong> — map SAML attributes to WordPress user fields (first name, last name, email, display name, plus arbitrary user_meta).</li>
<li><strong>Role mapping</strong> — assign WordPress roles based on SAML attribute values, with exact / contains / regex match types, per-IdP rule sets, deny-unmapped option, default-role fallback.</li>
<li><strong>Page access control</strong> — restrict pages, posts, and custom post types to specific roles or to “logged in via SSO” users; per-page meta box; <code>[oasso_restrict]</code> shortcode.</li>
<li><strong>WooCommerce integration</strong> (optional) — map SAML attributes to WooCommerce customer fields; auto-link SSO users to existing customers.</li>
<li><strong>Audit log</strong> with configurable retention.</li>
<li><strong>Force-SSO mode</strong> with emergency bypass via <code>OASSO_BYPASS</code> constant in <code>wp-config.php</code>.</li>
</ul>
<h4>Privacy</h4>
<p>This plugin’s only outbound HTTP requests go to the IdP metadata URL you enter: once when an administrator clicks “Fetch IdP Metadata from URL”, and — only if you turn on the optional certificate-rotation check for an IdP — on a recurring WP-Cron schedule that re-fetches that same URL. Certificate-rotation checks are disabled by default. No telemetry, no analytics, no calls to any third-party service. All configuration is stored in <code>wp_options</code> on your own site.</p>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0+</li>
<li>PHP 8.1+</li>
<li>A SAML 2.0 identity provider you control or have access to.</li>
</ul>
<h3>External Services</h3>
<p>This plugin is a SAML 2.0 Service Provider (SP). It sends no telemetry or analytics and never connects to any service operated by the plugin author. Its only external interactions are with the SAML Identity Provider (IdP) that you, the site administrator, configure — for example Microsoft Entra ID, Okta, OneLogin, Keycloak, ADFS, Shibboleth, or NetIQ Access Manager. There is no built-in or default IdP; the IdP is chosen and operated by you or your organisation.</p>
<h4>Identity Provider metadata fetch</h4>
<p>When an administrator clicks “Fetch IdP Metadata from URL” in the plugin’s admin screens, the plugin makes a single server-side HTTP GET request to the metadata URL the administrator entered. No site or user data is sent beyond a standard HTTP request; the response (SAML metadata XML) is parsed and stored in your site’s database. This never happens on the front end.</p>
<p>Optionally, you can enable a certificate-rotation check for an IdP (off by default). When enabled, WP-Cron re-fetches that same administrator-entered metadata URL on a schedule (for example daily) so the plugin can warn you before the IdP’s signing certificate expires or changes. This is the only automatic outbound request the plugin makes, it is opt-in per IdP, and it contacts only the metadata URL you configured.</p>
<h4>SAML single sign-on flow</h4>
<p>When a visitor signs in through SSO, their browser is redirected to your configured IdP (carrying a standard SAML AuthnRequest). After the visitor authenticates, the IdP returns a signed SAML assertion to your site, which the plugin validates and uses to create or update the corresponding WordPress user. The data exchanged is the SAML authentication request and response — which includes the user identifier and whatever attributes your IdP is configured to release. This exchange happens only when a visitor initiates an SSO login.</p>
<p>Because the IdP is a service you select and operate (or that your organisation operates), its terms of service and privacy policy are defined by that provider. Consult your chosen identity provider’s own documentation for those terms (for example, the privacy and terms pages of Microsoft Entra ID, Okta, OneLogin, etc.).</p>


Open Access SSO

Open-source SAML 2.0 SSO and access control. Map identity-provider attributes to WordPress roles. Multi-IdP, GPL-licensed.

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.

Open Access SSO vs SSO & SAML Login — Azure AD / Entra ID