Let your team sign in to WordPress with the company login they already use — one click, no extra password to manage, reset, or chase down. Open Access SSO connects your WordPress site to the identity provider your organisation already runs, so people log in through your trusted corporate sign-in ins
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.0 and PHP 8.1.
SourceWordPress plugins · Oct 25, 2026
01 / Source details
Aboutthistool.
Let your team sign in to WordPress with the company login they already use — one click, no extra password to manage, reset, or chase down.
Open Access SSO connects your WordPress site to the identity provider your organisation already runs, so people log in through your trusted corporate sign-in instead of juggling yet another WordPress password. It works with any standard SAML 2.0 identity provider — the plugin’s mature, fully-featured protocol — and, new in this release, with OpenID Connect providers too. That covers Microsoft Entra ID (Azure AD), Okta, OneLogin, Auth0, Keycloak, ADFS, Shibboleth, and NetIQ Access Manager (now OpenText), and it’s completely free and open-source, with no premium tier, no license key, and no upsell.
Everything below is included. Nothing is locked, metered, or “Pro.”
Why site admins choose it
Free, forever. Every feature ships in the GPLv2-or-later codebase — full role mapping, multi-IdP, access control, and more, at no cost. No paid plan, no per-site license, no feature gates.
Privacy-first by design. No telemetry, no analytics, no “phone home,” and no external CDN. Your configuration never leaves your site.
Works with the identity provider you already have. Point-and-click setup for any standards-compliant SAML 2.0 or OpenID Connect provider — no developer required for normal use.
Emergency admin access. A built-in bypass lets an admin get back in even if SSO is misconfigured — through a constant in wp-config.php or a pre-set bypass key.
Open and original. A clean-room, from-scratch implementation you can read and audit.
Connect it to your identity provider
One-click sign-in via SSO — let users log in through your IdP instead of, or alongside, the WordPress login form, with optional single logout that signs them out of both at once.
Multi-IdP support — connect several identity providers and let users pick with a login button or a simple ?idp=slug link.
Encrypted logins handled out of the box — including the encryption that modern providers (such as NetIQ Access Manager) turn on by default and that stock PHP can’t unwrap on its own, so encrypted sign-in just works.
Attribute mapping — map fields from your IdP (name, email, display name, and custom user data) straight onto WordPress profiles.
Control who gets in, and what they see
Powerful role mapping — automatically assign WordPress roles based on a user’s groups or attributes, with exact, contains, or regex matching, per-IdP rules, a default-role fallback, and an option to deny anyone who doesn’t match. A built-in safeguard means SSO won’t hand out admin-level roles unless you explicitly allow it.
Account linking — connect a first SSO login to an existing WordPress account by email (administrators are never auto-linked, for safety).
Page and content access control — restrict pages, posts, and custom post types to chosen roles or to “logged in via SSO” users, with a per-page editor control, the handy [oasso_restrict] shortcode, and category/tag-level rules. The same protection also covers the REST API, feeds, and oEmbed, so restricted content doesn’t leak through a side door.
Protected files and blocks — keep uploaded files behind a role check, and show or hide individual Gutenberg blocks by login status or role.
Email-domain and redirect rules — limit SSO sign-in to approved email domains and send users to the right place after login, per IdP.
WooCommerce integration (optional) — map attributes to billing and shipping details and auto-link customers by email; loads only when WooCommerce is active.
Stay in control after go-live
Certificate monitoring — track your IdP’s signing-certificate expiry, get warned before it changes, detect rotation on a daily or weekly check, and optionally pin a certificate for change control, with manual, auto-trust, grace-period, or require-approval handling.
Searchable audit log — a database-backed, filterable record of who signed in and when, with CSV export and a retention period you set.
Force-SSO with a safety net — require SSO across the site while keeping an emergency way back in (a constant in wp-config.php or a pre-set bypass key), so a misconfiguration doesn’t leave you stranded.
Import / export — back up or move your entire configuration as a single JSON file.
Easy setup, no coding
Add your identity provider three ways — upload its metadata XML, paste a metadata URL, or type the details in by hand — then register your site with the IdP using the SP metadata it generates for you. It’s all in the WordPress admin. (Developers also get a documented, stable hook API when they want it.)
Privacy you can verify
The plugin keeps to itself. The only time it reaches out to the network is when you ask it to fetch your IdP’s metadata from a URL, plus an optional, off-by-default certificate-rotation check that re-fetches that same address you entered. It never contacts the author or any third party, and every setting stays in your own site’s database. The two bundled libraries it relies on (both MIT-licensed) make no network calls at all.
Security without the homework
Incoming logins are fully validated before anyone is signed in — the plugin checks the digital signature, the sender, the intended audience, expiry, and replay protection, and accepts only strong, modern cryptography by default. Your SP private keys are encrypted at rest, and the public endpoints are guarded against common abuse. Sensible, secure defaults are on out of the box; the deeper knobs are documented for the rare cases you need them.
Free and open-source
Open Access SSO is licensed GPLv2 or later, with the full source available on Codeberg. There is no premium edition and nothing to buy — what you install is the complete plugin. Its only third-party libraries (xmlseclibs and phpseclib, both MIT-licensed) are bundled and make no network calls.
Requirements
WordPress 6.0 or newer
PHP 8.1 or newer
A SAML 2.0 identity provider you control or have access to
Documentation
Full guides, setup walkthroughs, and hardening advice live on Codeberg:
Full README / technical reference — https://codeberg.org/idgold/open-access-sso
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.
Identity Provider metadata fetch
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.
SAML single sign-on flow
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.).
Roadmap
Open Access SSO is actively developed. Here’s what’s planned next.
Under consideration
Automated user provisioning and deprovisioning (SCIM)
Scheduled group-to-role synchronisation
A branded identity-provider chooser for sites with multiple providers
Multi-factor authentication step-up hints
Deeper WooCommerce customer field mapping
Have a feature request? Open an issue on the project repository.
See it in action
Screenshots & previews.
Open Access SSO dashboard - SSO status, configured Identity Providers, and module toggles.Identity Provider configuration - SAML endpoints, signing certificate, and attribute mapping.Role mapping rules - assign WordPress roles from SAML attribute values.Per-page access control in the editor - restrict by role or require SSO login.
02 / Source details
Gettingstarted.
01Download the .zip and upload via Plugins → Add New → Upload Plugin, or extract into /wp-content/plugins/open-access-sso/ .
02Activate through the Plugins menu.
03Navigate to Tools → Open Access SSO to configure.
04Add an identity provider: upload the IdP metadata XML, paste a metadata URL, or enter the IdP fields manually.
05Copy the SP metadata URL shown on the dashboard and register your WordPress site as a Service Provider in your IdP.
06Test sign-on using the SSO button on the login page.
03 / Source details
Frequently asked questions.
Is it really free?
Yes — completely. There is no premium tier, no license key, and nothing to unlock. Every feature you read about ships in the GPLv2-or-later codebase: role mapping, multi-IdP, access control, the audit log, WooCommerce integration, all of it. The full source is on Codeberg, so you can see exactly what you’re installing.
Will it work with my identity provider?
Almost certainly. Open Access SSO speaks standard SAML 2.0, so it works with any standards-compliant identity provider — Microsoft Entra ID (Azure AD), Okta, OneLogin, Keycloak, ADFS, Shibboleth, and NetIQ Access Manager (now OpenText), among others. There’s no built-in or default IdP; you bring your own, and you point the plugin at it. The identity-provider setup guide (see Documentation) walks through the common providers step by step.
Do I need to be a developer to set it up?
No. Setup is point-and-click in the WordPress admin. You add your identity provider one of three easy ways — upload its metadata XML file, paste a metadata URL, or type the details in by hand — then copy the SP metadata the plugin generates and register your site with your IdP. No code required for normal use. (If you are a developer, there’s a documented, stable hook API waiting for you.)
Is my users’ data safe, and does it track anyone?
Yes, and no tracking whatsoever. The plugin has no telemetry, no analytics, no “phone home,” and no external CDN. The only time it ever reaches out to the network is when you ask it to fetch your IdP’s metadata from a URL — plus an optional, off-by-default certificate-rotation check that re-fetches that same address you entered. It never contacts the plugin author or any third party, and every setting stays in your own site’s database. Sign-ins are validated end to end before anyone is let in, and your SP private keys are encrypted at rest. For the full details, see the security & hardening guide in Documentation.
What if SSO locks me out?
You have a built-in emergency way back in. You can either add define( 'OASSO_BYPASS', true ); to wp-config.php to switch off forced SSO entirely, or set a Bypass Secret Key on the dashboard ahead of time and visit /wp-admin/?oasso_bypass_key=YOUR_KEY to get back in without touching any files. The key route is rate-limited per IP address to frustrate brute-force guessing. The troubleshooting guide (see Documentation) covers recovery in detail.
Can I use more than one identity provider?
Yes. Configure as many IdPs as you need under Tools → Open Access SSO → Identity Providers. Your users pick the right one with a button on the login page or via a simple ?idp=slug link.
Can I assign WordPress roles automatically from my IdP?
Yes — that’s one of the headline features. Map WordPress roles from the groups or attributes your IdP sends, using exact, contains, or regex matching, with per-IdP rule sets, a default-role fallback, and an option to deny anyone who doesn’t match a rule. For safety, SSO won’t grant admin-level roles unless you explicitly turn that on, and existing administrator accounts are never auto-linked to an SSO login.
Does it support encrypted logins?
Yes, out of the box — including the modern encryption that some providers (such as NetIQ Access Manager) turn on by default and that stock PHP can’t unwrap on its own. The plugin bundles a small MIT-licensed library to handle exactly that, so encrypted sign-in just works where a plain PHP setup would fall short. Encrypted user identifiers are supported too.
Does it work with NetIQ Access Manager?
Yes. NetIQ Access Manager (now part of OpenText) is a standard SAML 2.0 identity provider and is fully supported, including its default encrypted assertions. One clarification: NetIQ Identity Manager (sometimes called “IDM”) is a separate user-provisioning product, not a SAML IdP — it’s Access Manager that acts as the identity provider here.
Can I keep an eye on certificates and sign-in activity?
Yes. The plugin tracks each IdP’s signing-certificate expiry and can warn you before it changes, detecting rotation on a daily or weekly check with your choice of manual, auto-trust, grace-period, or require-approval handling — and you can pin a specific certificate if you want strict change control. A searchable, database-backed audit log records who signed in and when, with CSV export and a retention period you set.
Where do protected media files go?
When a page with attached media is restricted, the plugin physically moves those files out of the public uploads folder into a private directory ( uploads/oasso-private/ ) with an unguessable name, and serves them through an access-checked gateway URL. Direct links to the old file location stop working for everyone — that is the point. Unprotecting the page (or uninstalling the plugin) moves the files back. Files uploaded before version 2.4.0 are moved only when you click “Relocate existing protected media” under Access Control. After relocating, purge your page cache/CDN. If you deactivate the plugin, relocated files are unreachable (but not exposed) until you reactivate or restore them first.
Is this related to the old “OpenSSO” product from Sun or Oracle?
No. Open Access SSO is an independent open-source project. It is not affiliated with, and is not a continuation of, Sun Microsystems’ or Oracle’s discontinued “OpenSSO” product — the similar name is coincidental.
Website LLMs.txt and LLMs-Full.txt Generator is an LLMs.txt generator and llms-full.txt generator for WordPress. It helps site owners generate, manage, preview, validate, and serve AI discovery files from published public content. Use it to create structured /llms.txt and optional /llms-full.txt end
EngageDock AI is a customizable floating contact widget for WordPress websites that want more leads and faster visitor communication. It helps small businesses turn website traffic into calls, texts, emails, and callback requests from one clean contact panel. Key Features: Click-to-Call – One tap ca
Altify AI is an auto ALT text and AI ALT text plugin for WordPress images. It helps generate descriptive image ALT text for accessibility and image SEO. Use bulk image ALT text tools for your Media Library, generate featured image ALT text automatically, and scale WooCommerce image ALT updates with
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati
