| 开发者 | jfwenisch |
|---|---|
| 更新时间 | 2026年6月24日 01:41 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wenisch-tech/keystone-oidc/.well-known/openid-configuration) for automatic client configurationopenid, profile, email/wenisch-tech/keystone-oidc/.well-known/openid-configuration/wenisch-tech/keystone-oidc/oauth/authorize/wenisch-tech/keystone-oidc/oauth/token/wenisch-tech/keystone-oidc/oauth/userinfo/wenisch-tech/keystone-oidc/oauth/jwks/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.
Roles are not currently emitted. The plugin does not expose WordPress roles or capabilities in UserInfo or ID tokens.
keystone-oidc folder to /wp-content/plugins/keystone-oidc.zip from the GitHub Releases page and upload it via Plugins → Add New → Upload Plugin.Authorization Code Flow (with and without PKCE). This is the most secure flow and suitable for all application types.
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.
Yes – you can create as many OIDC clients as you need from the admin panel.
All previously issued tokens will immediately become invalid. Use the Settings page to rotate keys when needed (e.g., after a security incident).
Yes, both S256 and plain code challenge methods are supported.