Linux 软件免费装

AH JWT Auth

开发者 andrewheberle
更新时间 2026年7月7日 07:21
捐献地址: 去捐款
PHP版本: 8.0 及以上
WordPress版本: 7.0.0
版权: GPLv3 or later
版权网址: 版权信息

标签

login authentication sso jwt auth

下载

1.3.0 1.1.0 1.2.0 1.2.1 1.2.2 1.4.1 1.5.1 1.5.4 1.0.3 1.3.1 1.5.0 1.4.0 1.5.2 1.5.3 1.6.0 2.0.0 2.1.0 2.2.0 2.3.0

详情介绍:

This plugin allows sign in to WordPress using a JSON Web Token (JWT) contained in a HTTP Header that is added by a reverse proxy that sits in front of your WordPress deployment. Authentication and optionally role assignment is handled by claims contained in the JWT. If configured, the plugin also validates the JWT aud and iss claims against the expected application audience and JWT issuer values. Verification of the JWT is handled by either: During the login process if the user does not exist an account will be created with a matching role from the JWT, unless automatic user creation has been disabled in the plugin settings. If the JWT did not contain a role claim then user is created with the role set in the plugin settings (by default this is the subscriber role). Automatic user creation is enabled by default for backwards compatibility. It can be disabled when user provisioning should remain manual.

升级注意事项:

1.0.3 Initial public release 1.0.2 Internationalisation for strings 1.0.1 Better handling or errors.

常见问题:

What header is the JWT retrieved from?

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.

What claims should the JWT contain?

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.

What signature algorithms are supported to verify the JWT?

Currently only the HS256 and RS256 algorithms are supported.

更新日志:

2.3.0 2.2.0 2.1.0 2.0.0 1.6.0 1.5.4 1.5.3 1.5.1 1.5.0 1.4.1 1.3.1 1.3.0 1.2.2 1.2.1 1.2.0 1.1.0 1.0.3 1.0.2 1.0.1 1.0.0