idgold

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.
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.
<h4>What it does</h4>
<ul>
<li>SAML 2.0 SP with HTTP-Redirect and HTTP-POST bindings, signed AuthnRequests, signed/encrypted assertion handling, SP-initiated and IdP-initiated Single Logout.</li>
<li>Multi-IdP — configure multiple identity providers, let users choose via a button or URL parameter (<code>?idp=slug</code>).</li>
<li>Attribute mapping — map SAML attributes to WordPress user fields (first name, last name, email, display name, plus arbitrary user_meta).</li>
<li>Role mapping — 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>Page access control — 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>WooCommerce integration (optional) — map SAML attributes to WooCommerce customer fields; auto-link SSO users to existing customers.</li>
<li>Audit log with configurable retention.</li>
<li>Force-SSO mode with emergency bypass via <code>OASSO_BYPASS</code> constant in <code>wp-config.php</code>.</li>
</ul>
<h4>Privacy</h4>
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.
<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>
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.
<h4>Identity Provider metadata fetch</h4>
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.
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.
<h4>SAML single sign-on flow</h4>
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.
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.).

Open Access SSO

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

Airton Vancin Junior

SSO JumpCloud – Enterprise SAML & SCIM is a powerful Enterprise-ready plugin that effortlessly connects your WordPress site with JumpCloud using SAML 2.0.
Designed for security-conscious organizations, it provides seamless single sign-on (SSO), automated user provisioning, and advanced role mapping. With our newly released Enterprise Premium Edition, you can now manage complex access requirements and maintain detailed audit trails.
Key Features: 
* Easy Setup: Connect to JumpCloud in minutes using Entity ID, SSO URL, and Certificate. 
* Automatic User Creation: New users from JumpCloud are automatically created in WordPress upon their first login. 
* Secure Authentication: Uses verified SAML 2.0 protocols to ensure your data stays safe. 
* Developer Friendly: Clean code, hooks for customization, and minimalist design.
<h3>Premium Features</h3>
Unlock the full power of your enterprise identity management with: 
* Group-Based Access Control: Restrict login access to specific JumpCloud groups. 
* Role-Based Redirects: Define custom landing pages for different user roles. 
* Automated Role Mapping: Dynamically assign WordPress roles based on JumpCloud groups. 
* Comprehensive Audit Logs: Track every SSO login attempt with detailed metadata. 
* Enterprise Support: Priority assistance for complex deployments.
<h3>Premium Subscription</h3>
The Premium features are available via a monthly or annual subscription.
How to Activate: 
1. Go to the Premium Features tab in the plugin settings. 
2. If you don’t have a subscription yet, use the secure Stripe pricing table to subscribe. 
3. Once subscribed, simply click the “Check Subscription Status” button. 
4. The plugin will automatically verify your subscription using your administrator email and activate all premium features instantly. 
5. You can manage your subscription at any time via the Stripe Customer Portal link provided in the same tab.
<h3>Installation & Setup Guide</h3>
Configuring Enterprise SSO and Provisioning requires a few steps in both JumpCloud and WordPress. Follow this guide for a flawless setup.
<h3>Part 1: JumpCloud Configuration (SAML 2.0)</h3>
<ol>
<li>Log in to your JumpCloud Admin Portal.</li>
<li>Navigate to SSO Applications and click “+” to add a new application.</li>
<li>Search for SAML 2.0 and select Custom SAML App.</li>
<li>In the General Info tab, name it “WordPress SSO”.</li>
<li>In the SSO tab, enter the following (copy these from your WordPress Plugin settings):
<ul>
<li>IdP Entity ID: Your unique ID (e.g., <code>wp-sso-your-site</code>).</li>
<li>SP Entity ID: Copy from Plugin (usually your Site URL).</li>
<li>ACS URL: Copy from Plugin (usually <code>https://your-site.com/?jumpssco_acs</code>).</li>
<li>SAMLSubject NameID: Default to <code>email</code>.</li>
<li>SAMLSubject NameID Format: <code>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</code>.</li>
</ul>
</li>
<li>In Attributes, add:
<ul>
<li><code>email</code> -> <code>email</code></li>
<li><code>firstname</code> -> <code>firstname</code></li>
<li><code>lastname</code> -> <code>lastname</code></li>
</ul>
</li>
<li>Click save and then export Metadata or copy the SSO URL, Entity ID, and download the IDP Certificate.</li>
</ol>
<h3>Part 2: WordPress Plugin Setup</h3>
<ol>
<li>Install and Activate the plugin.</li>
<li>Go to Settings > SSO JumpCloud.</li>
<li>In the General tab, paste the IDP Entity ID, IDP SSO URL, and the X.509 Certificate obtained from JumpCloud.</li>
<li>Click Save Settings.</li>
<li>Use the “Test Configuration” button to ensure the connection is established.</li>
</ol>
<h3>Part 3: SCIM Provisioning (Enterprise Feature)</h3>
Note: Requires an active Enterprise Premium subscription. 
1. In the plugin settings, go to the SCIM Provisioning tab. 
2. Toggle “Enable SCIM Provisioning” to ON. 
3. Copy the SCIM Base URL and the Bearer Token. 
4. In JumpCloud, go to your Application’s Identity Management tab. 
5. Select SCIM 2.0. 
6. Paste the Base URL and Bearer Token. 
7. Test the connection in JumpCloud and click Activate.
<h3>Part 4: Final Testing</h3>
<ul>
<li>Open an Incognito/Private browser window.</li>
<li>Go to your WordPress login page.</li>
<li>Click the “Login with JumpCloud” button.</li>
<li>If successful, you will be authenticated and redirected to your dashboard!</li>
</ul>

SSO JumpCloud – Enterprise SAML & SCIM

Securely connect WordPress with JumpCloud for Enterprise SSO via SAML 2.0 and automated user provisioning via SCIM.

Open Access SSO vs SSO JumpCloud – Enterprise SAML & SCIM