Frontegg

<p>Frontegg SAML SSO replaces the default WordPress login and logout experiences with seamless SAML authentication via <a href="https://frontegg.com" rel="nofollow ugc">Frontegg</a>.</p>
<p>This plugin is designed for modern SaaS and enterprise WordPress environments where you need to enforce login via an external identity provider (IdP).</p>
<p>It includes:<br />
– 🔐 Secure SAML 2.0 login and logout<br />
– 📋 Admin-friendly configuration of SSO URLs and certificate<br />
– 📎 Auto-generated SP (Service Provider) values (Entity ID, ACS URL, SLO URL)<br />
– 🧭 Redirect control after logout<br />
– 🔄 Auto-redirects from <code>wp-login.php</code> to Frontegg<br />
– ✨ Clean and accessible admin UI using native WordPress components</p>
<h3>License</h3>
<p>This plugin is licensed under the GPL v2.0 or later. See LICENSE.txt for details.</p>


Frontegg SAML SSO

Replace the WordPress login and logout flows with secure SAML-based authentication via Frontegg. Easily configure your SSO app from the admin panel.

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.

Frontegg SAML SSO vs Open Access SSO