Àpèjúwe
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.
Verification of the JWT is handled by either:
- a shared secret key
- retrieving a JSON Web Key Set (JWKS) from a configured URL
During the login process if the user does not exist an account will be created with a matching role from the JWT.
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).
Àwọn àwòrán ìbòjú
FAQ
-
What header is the JWT retrieved from?
-
By default the plugin looks for the JWT in the
Authorizationheader as follows:Authorization: Bearer <JWT Here>However the token may be retrieved from a configurable HTTP header, for example integration with Cloudflare Access would use
theCf-Access-Jwt-Assertionheader. -
What should the JWT contain?
-
The JWT must contain at least an
emailclaim and may also contain aroleclaim:{ "email": "admin@example.com", "role": "admin" } -
What signature algorimths are supported to verify the JWT?
-
Currently only the HS256 and RS256 alorithms are supported.
Àwọn àgbéyẹ̀wò
Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.
Àwọn Olùkópa & Olùgbéejáde
“AH JWT Auth” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.
Àwọn OlùkópaTúmọ̀ “AH JWT Auth” sí èdè rẹ.
Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?
Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.
Àkọsílẹ̀ àwọn àyípadà
1.5.4
- Fix bug that meant role was not being set based on selection
1.5.3
- Make JWKS refresh function public
1.5.1
- Fixes for JWKS refresh process
1.5.0
- Add WP cron job to refresh JWKS daily
1.4.1
- Update dependencies to resolve security issue
1.3.1
- Clean-ups and bug fixes
1.3.0
- Allow setting default role for auto-created users
1.2.2
- Version bump for plugin update on WordPress.org
1.2.1
- Version bump for plugin update on WordPress.org
1.2.0
- Fix a bug where an invalid JSON response from JWKS URL was cached leading to broken SSO
1.1.0
- Make login process more efficient by skipping JWT verify/login if user is already authenticated
1.0.3
- Initial release on WordPress.org
1.0.2
- Added internationalisation for strings
- Changes based on WordPress.org plugin submission feedback
1.0.1
- Added more error checking
1.0.0
- First version
