Linux 软件免费装
Banner图

Keystone OIDC

开发者 jfwenisch
更新时间 2026年11月20日 23:31
PHP版本: 7.4 及以上
WordPress版本: 7.1.5
版权: GPLv2 or later
版权网址: 版权信息

标签

authentication sso oauth2 oidc openid-connect

下载

3.1.0 2.3.6 2.3.2 2.3.1 2.3.4 2.2.2 2.3.0 2.3.3 2.3.5 2.4.0 2.4.1 2.2.1 3.0.0 3.0.1

详情介绍:

Keystone OIDC transforms your WordPress installation into a fully-featured OpenID Connect (OIDC) identity provider, allowing other applications to authenticate users via your WordPress user database. Key Features Quick Start
  1. Install and activate the plugin
  2. Go to OIDC Provider → Add Client in your WordPress admin
  3. Enter your application name and redirect URI(s)
  4. Copy the generated Client ID and Client Secret (shown once)
  5. Configure your OIDC client application with the discovery URL shown in the settings
Documentation Full documentation (installation, client types, endpoint reference, upgrade notes and troubleshooting) is available at keystone-oidc.wenisch.tech. Endpoints All URLs are relative to your WordPress site root. Compatibility aliases are also routed under /wenisch-tech/keystone-oidc/protocol/openid-connect/* for clients that still derive Keycloak-style paths from the custom issuer URI. These aliases are not advertised in discovery. UserInfo Example For openid profile email, /wenisch-tech/keystone-oidc/oauth/userinfo returns: { "sub": "42", "name": "Jane Doe", "given_name": "Jane", "family_name": "Doe", "preferred_username": "jane", "email": "jane@example.com", "email_verified": true } sub is the WordPress user ID as a string, preferred_username is the WordPress user_login, and email is the WordPress user_email. With the roles scope, the response also contains a flat roles array of WordPress role slugs: "roles": ["editor"] The roles scope is opt-in: tick it in the client's Allowed Scopes and request it from your application (for example scope=openid profile email roles). Capabilities are not exposed, and WordPress has no native groups, so no groups claim is sent.

安装:

  1. Upload the keystone-oidc folder to /wp-content/plugins/
  2. Activate the plugin through the Plugins menu
  3. Navigate to OIDC Provider in the admin sidebar to create your first client
Alternatively, download the keystone-oidc.zip from the GitHub Releases page and upload it via Plugins → Add New → Upload Plugin.

升级注意事项:

1.0.0 Initial release.

常见问题:

What OIDC flows are supported?

Authorization Code Flow (confidential clients authenticate with their secret, public clients use PKCE). This is the most secure flow and suitable for all application types.

Where is the client secret stored?

Client secrets are hashed using WordPress's password hashing (bcrypt). The plaintext secret is shown only once upon creation or reset and is never stored in the database.

Can I send WordPress roles to my application?

Yes. Enable the roles scope for the client and request it. The user's WordPress roles (such as administrator or editor) are sent as a roles array in the ID token and UserInfo response. Developers can change the list with the keystone_oidc_user_roles filter.

Does this plugin support multiple clients?

Yes – you can create as many OIDC clients as you need from the admin panel.

What happens if I rotate signing keys?

All previously issued tokens will immediately become invalid. Use the Settings page to rotate keys when needed (e.g., after a security incident).

Is PKCE supported?

Yes, both S256 and plain code challenge methods are supported. Public clients (no secret) must use S256. Confidential clients must always authenticate with their client secret at the token endpoint.

What are public and confidential clients?

A confidential client is a server-side application that can keep a secret. A public client (single-page or mobile app) cannot, so it uses PKCE instead. Set the type per client under OIDC Provider > Clients. Existing clients are treated as confidential after an update.

Can native mobile apps use Keystone OIDC?

Yes. Register a public client and use either an https redirect (Android App Links / iOS Universal Links) or a reverse-domain private-use scheme such as com.example.app:/oauth2redirect (RFC 8252). PKCE with S256 is mandatory for public clients.

Can I customize who may sign in or what is in the tokens?

Yes. Keystone OIDC provides filters to allow or deny sign-in (keystone_oidc_authorize_user), re-check users on refresh (keystone_oidc_refresh_allowed), add custom claims to the ID token, access token and UserInfo response, and change token lifetimes. KEYSTONE_OIDC_Token_Manager::revoke_user_tokens() revokes a user's tokens, which also happens automatically when a user is deleted or changes their password. See the "Extending with hooks" page in the documentation.

更新日志:

3.1.0 3.1.0 (2026-11-20) Features Bug Fixes Documentation 3.0.1 3.0.1 (2026-11-19) Documentation 3.0.0 3.0.0 (2026-11-19) ⚠ BREAKING CHANGES Every client now has a type (confidential or public). Existing clients are migrated to confidential, so clients that relied on PKCE without a secret (SPAs, mobile apps) must be switched to "Public" in the admin UI. Also: reject unknown code_challenge_method values and malformed PKCE challenges/verifiers, URL-decode HTTP Basic credentials, reject client_id mismatches between header and body, advertise "none" in discovery. Add Docusaurus documentation (docs/, docs-site/) and a GitHub Pages workflow. Bug Fixes 2.4.1 2.4.1 (2026-11-18) 2.4.0 2.4.0 (2026-11-15) Features 2.3.6 2.3.6 (2026-10-18) 2.3.5 2.3.5 (2026-09-24) 2.3.4 2.3.4 (2026-08-21) Bug Fixes 2.3.3 2.3.3 (2026-07-14) 2.3.2 2.3.2 (2026-06-23) Bug Fixes 2.3.1 2.3.1 (2026-06-14) Documentation 2.3.0 2.3.0 (2026-06-14) Features Bug Fixes 2.2.2 Released on 2026-06-12. Bug Fixes Documentation 1.0.0