SSO Enforcer for Jetpack -- WordPress 插件

开发者	alconicdevelopment
更新时间	2026年11月7日 04:38
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

Jetpack's Secure Sign-On (SSO) lets people log in to your site with their WordPress.com account, but it only adds that as an option. The username and password form stays available, so anyone with a password can still sign in without WordPress.com and skip its two-step authentication and account protections. SSO Enforcer for Jetpack makes WordPress.com sign-in the only way in. While enforcement is on, it:

Sends wp-login.php visitors straight to WordPress.com to sign in
Hides the local username and password form
Blocks password logins over XML-RPC and application passwords, which skip wp-login.php

Use it when you want every account on your site to sign in through WordPress.com, for example to require two-step authentication for all administrators and editors. Jetpack's own connection to WordPress.com keeps working. If an integration still needs a username and password or an application password, check Allow application passwords and XML-RPC password logins on the settings page. The plugin only enables enforcement when Jetpack is installed, the site is connected to WordPress.com, Jetpack WordPress.com login (SSO) is enabled, and the enabling administrator is linked to WordPress.com. Deactivating or deleting the plugin immediately stops enforcement and restores your previous Jetpack SSO behavior.

安装:

Install and activate Jetpack and enable WordPress.com login (SSO) under Jetpack → Settings → Security.
Install this plugin from the WordPress.org plugin directory, or upload the sso-enforcer-for-jetpack folder to /wp-content/plugins/.
Activate the plugin through the Plugins screen in WordPress.
Go to Settings → SSO Enforcer for Jetpack.
Confirm all prerequisites pass, then enable the toggle.

常见问题:

更新日志:

1.1.2

The upgrade notice about XML-RPC and application password logins now has a close (X) button and stays dismissed.

1.1.1

Reword the plugin description to explain that it makes WordPress.com sign-in mandatory, rather than optional as with Jetpack SSO alone.

1.1.0

Block password logins over XML-RPC and application passwords while enforcement is on, with a setting to allow them again.
Show a one-time notice to administrators of sites that already had enforcement on.
Remove plugin options from every site when uninstalled on multisite.
Pin GitHub Actions checkout to a commit SHA and stop persisting its credentials.
Tested up to WordPress 7.1; checked for compatibility with PHP 7.4 through 8.5.

1.0.8

Scope settings notices to the current administrator.
Redirect after saving settings to avoid duplicate submissions.
Treat stored option value 0 as disabled.
Use Jetpack Status APIs for staging and development site warnings.
Pin the WordPress.org deploy GitHub Action to a commit SHA.
Keep enforcement on when re-saving; SSO-linked admin checks apply only when enabling.

1.0.7

Restrict GitHub Actions workflow token permissions to read-only.

1.0.6

Add Settings link on the Plugins list screen.

1.0.5

Fix translation loading notice on WordPress 6.7+ when enforcement is enabled.

1.0.4

Update plugin author to Alconic Development.
Update WordPress.org contributor to alconicdevelopment.

1.0.3

Rename plugin to SSO Enforcer for Jetpack (sso-enforcer-for-jetpack) for WordPress.org review.
Migrate stored options from previous plugin slugs.

1.0.2

Update Tested up to for WordPress 7.0 compatibility.

1.0.1

Rename plugin to Force SSO Login for WordPress.org trademark compliance.
Align WordPress version headers with Plugin Check requirements.

1.0.0

Initial release.

SSO Enforcer for Jetpack

标签

下载

详情介绍:

安装:

升级注意事项:

常见问题:

更新日志: