Plugin info

Total downloads: 2,336
Active installs: 10
Total reviews: 0
Average rating: 0
Support threads opened: 0
Support threads resolved: 0 (0%)
Available in: 1 language(s)
Contributors: 1
Last updated: 3/5/2025 (301 days ago)
Added to WordPress: 4/22/2021 (4 years old)
Minimum WordPress version: 4.7
Tested up to WordPress version: 6.7.4
Minimum PHP version: 7.0

Maintenance & Compatibility

Maintenance score

Stale • Last updated 301 days ago

38/100

Is AH JWT Auth abandoned?

Likely maintained (last update 301 days ago).

Compatibility

Requires WordPress: 4.7
Tested up to: 6.7.4
Requires PHP: 7.0

Similar & Alternatives

Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.

Simple JWT Login MailPoet – Login users from newsletter
Rating 0.0/5 (0 reviews)Active installs 0
JWT Authentication for WP REST API
Rating 4.4/5 (51 reviews)Active installs 60,000
REST API Authentication for WP – JWT Auth and more
Rating 4.4/5 (71 reviews)Active installs 20,000
JWT Auth – WordPress JSON Web Token Authentication
Rating 5.0/5 (22 reviews)Active installs 6,000
Simple JWT Login – Allows you to use JWT on REST endpoints.
Rating 5.0/5 (46 reviews)Active installs 4,000
Firebase Authentication
Rating 4.0/5 (20 reviews)Active installs 500

Description

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).

Installation

No installation instructions available

Frequently Asked Questions

What header is the JWT retrieved from?

By default the plugin looks for the JWT in the Authorization header 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
the Cf-Access-Jwt-Assertion header.

What should the JWT contain?

The JWT must contain at least an email claim and may also contain a role claim:

{
    "email": "[email protected]",
    "role": "admin"
}

What signature algorimths are supported to verify the JWT?

Currently only the HS256 and RS256 alorithms are supported.

Review feed

No reviews available

Screenshots

  1. This example shows a configuration with a WordPress install behind Cloudflare Access for SSO via JWT

    This example shows a configuration with a WordPress install behind Cloudflare Access for SSO via JWT

Changelog

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