| 开发者 | andrewheberle |
|---|---|
| 更新时间 | 2026年10月24日 15:05 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
aud and iss claims against the expected application audience and JWT issuer values.
Verification of the JWT is handled by either:
By default the plugin looks for the JWT in the Authorization header as follows:
Authorization: Bearer
However the token may be retrieved from a configurable HTTP header, for example to integrate with Cloudflare Access, which was the original target for this plugin, you would configure the use of the Cf-Access-Jwt-Assertion header.
The JWT must contain at least an email claim and may also contain a role claim:
{
"iss": "example.com",
"aud": "example-audience-id",
"email": "admin@example.com",
"iat": 1356999524,
"nbf": 1357000000,
"role": "admin"
}
The aud and iss claims are only required when a JWT Audience and/or Issuer value has been configured in the plugin settings, however as they are standard JWT claims it is recommended to set these options to verify those claims exist and are valid.
Currently only the HS256 and RS256 algorithms are supported.
Deactivating the plugin leaves its settings in place, so reactivating it picks up where you left off. Deleting the plugin removes all of its settings, including the JWT private secret, from every site in a multisite network. User accounts the plugin created from JWTs are kept, as they belong to the site.