by Jessica 1 (0 reviews)

Cross-Site SSO for OpenID Connect

Name: Cross-Site SSO for OpenID Connect
Author: Jessica

The plugin provides a single sign-on, logout and signed cross-site connection for separate WordPress installs sharing one OpenID Connect provider.

Cross-Site SSO for OpenID Connect ranks #60,158 among WordPress.org plugins with 1+ active installations, is #7,179 of 13,811 in the E-commerce category, a 1/5 rating from 0 reviews, and was last updated Oct 14, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.0.0 Current Version v1.0.0

Updated 1 week ago Last Update on 14 Oct, 2026

Refreshed 7 hours ago Last Refreshed on

#7,179 of 13,811 in E-commerce Downloads -44.1% this week Actively maintained

View on WordPress.org

Rank

#60,158

— No change

Active Installs

-1%

KW Avg Position

53.7

0.3 better

Downloads

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 30%

0+ 10+

47,221

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 7 more installs to reach 10+

Rank Changes

Current #60,158

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Oct 14, 2026
Requires WP: 5.9+
Tested Up To: 7.1
PHP Version: 7.4 or higher
Author: Jessica

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

Single Sign-on oidc openid connect sso woocommerce

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,762

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)

Google for WooCommerce

800K+ installs

#74

WooPayments: Integrated WooCommerce Payments

800K+ installs

#76

WooCommerce PayPal Payments

800K+ installs

#81

WooCommerce Stripe Payment Gateway

700K+ installs

#85

WooCommerce Tax (formerly WooCommerce Shipping & Tax)

500K+ installs

#116

View all Ecommerce plugins

Frequently Asked Questions

Common questions about Cross-Site SSO for OpenID Connect

In wp-config.php, if you can edit. A signing key in the options table is in every database backup and every export handed to a contractor, and is reachable by any vulnerability that discloses options. If you cannot edit that file, many managed hosts allow plugin installation and no file access at all, set it under Tools > Cross-Site SSO > Settings instead. The option is stored with autoload off and is never displayed again after saving. A constant, when defined, always wins and the field becomes read-only. The screen shows a short fingerprint of the secret, so you can confirm every site holds the same value. When the fingerprints match, this mean matching secrets; while a mismatch explains the 403 errors.

The status code is the diagnosis, and these are unrelated: 404 — no REST route on that site, so the plugin is not installed or not activated. 503 — the plugin is installed but has no secret or not configured yet. 403 — the request was signed, received, but refused. You have to work through the sites in order: install and activate on sites, then configure and test.

Yes, each site resolves each setting independently: the constant if one is defined, the stored option otherwise. A site with file access can use constants while another uses the Settings screen, as long as the secret matches, compare the fingerprints to confirm.

They interoperate across versions: the signing format, headers, REST routes and logout tickets have not changed since 1.0.0. When running the same version everywhere is still recommended, because newer versions add local behavior (for example, refusing silent sign-on for administrators) that only applies where installed.

Yes, per site. What you must not do is install it in both places on the same site: the classes then load twice from two paths, which is a fatal error. The plugin detects this, stops loading, and shows an admin notice naming the file that is actually running.

Yes, every setting can be entered on the Settings tab. The plugin only needs to be installable and able to make outbound HTTPS requests.

Whatever Settings > General > New User Default Role says on that site normally subscriber. OpenID Connect Generic does not set a role when it creates the account, so wp_insert_user() falls back to that option., changing the setting is usually the whole answer, no code is needed. In order to decide the role per user instead, use the ls_sso_map_roles filter. The plugin runs on every SSO login, including when no role claim is configured: add_filter( 'ls_sso_map_roles', function ( $roles, $incoming, $user ) { return in_array( 'staff', $incoming, true ) ? array( 'editor' ) : array( 'customer' ); }, 10, 3 ); Administrators are never reassigned by this filter, so a misconfigured provider cannot demote a user. If you map from a provider claim, note that Auth0 silently drops custom claims namespaced under an Auth0 domain — auth0.com, webtask.io and webtask.run

arrives, and role mapping then appears broken with no error.

No, WooCommerce is only needed for the optional order-history feature, and only on the one site that runs the store.

The plugin is built for the opposite case: separate installations with separate databases. A multisite network already shares users, sessions and logout through WordPress core, and does not need this plugin.