Hidayat Mahetar

HeadlessKey – JWT Auth extends the REST API to provide a robust and secure authentication system using JSON Web Tokens (JWT). Designed for Headless WordPress, it enables seamless user authentication, registration, and session management via standard REST endpoints.
<h3>Key Features</h3>
<ul>
<li>Standard JWT Authentication: Secure user authentication using industry-standard RFC 7519 tokens.</li>
<li>Multiple Algorithms: Support for <code>HS256</code>, <code>RS256</code>, and <code>ES256</code> signing algorithms.</li>
<li>Comprehensive Endpoints: Ready-to-use endpoints for Login, Register, Token Refresh, and Password Management.</li>
<li>Single Sign-On (SSO): Connect multiple sites with a secure, headers-based SSO exchange mechanism.</li>
<li>Role-Based Access Control (RBAC): Configure public or authenticated access for every endpoint.</li>
<li>Brute Force Protection: Protects against attacks by locking users/IPs after failed attempts.</li>
<li>Activity Logs: Detailed audit trail of all authentication events, including IP and device data.</li>
<li>Security Webhooks: Real-time JSON events sent to your external services for monitoring key actions.</li>
<li>Device Limits: Restrict the number of active devices/sessions per user.</li>
<li>Developer Friendly: Extensive hooks and filters for deep customization.</li>
</ul>
<h3>Configuration</h3>
<h3>Secret Key</h3>
The plugin uses a secret key to sign tokens. By default, a secure random key is generated. For better security and consistency across environments, define your key in <code>wp-config.php</code>:
<pre><code>define('headlesskey_SECRET_KEY', 'your-long-random-secure-string');
</code></pre>
You can generate a strong salt here: <a href="https://api.wordpress.org/secret-key/1.1/salt/" rel="nofollow ugc">WordPress Salt Generator</a>
<h3>CORS Support</h3>
Cross-Origin Resource Sharing (CORS) is enabled by default to allow frontend applications to connect. To disable or customize it via constant:
<pre><code>define('headlesskey_CORS', true); // or false to disable
</code></pre>
<h3>REST API Namespace</h3>
By default, endpoints are under <code>wp-json/wpauthapi/v1</code>. You can customize this namespace:
<pre><code>define('headlesskey_REST_NAMESPACE', 'my-custom-auth');
define('headlesskey_REST_VERSION', 'v2');<h3>Endpoints</h3>
</code></pre>
The plugin adds the following endpoints under the <code>/wp-json/headlesskey/v1</code> namespace:
 Endpoint 
 HTTP Verb 
 Description
 <code>/token</code> 
 POST 
 Login: Exchange username/password for a JWT.
 <code>/token/validate</code> 
 POST 
 Validate: Check if a token validity.
 <code>/token/refresh</code> 
 POST 
 Refresh: Exchange a valid token for a new one (rotation).
 <code>/token/revoke</code> 
 POST 
 Logout: Invalidate a specific token.
 <code>/register</code> 
 POST 
 Register: Create a new user account.
 <code>/login</code> 
 POST 
 Profile: Login and get full user profile data in one request.
 <code>/forgot-password</code> 
 POST 
 Recover: Request a password reset via Link or OTP.
 <code>/reset-password</code> 
 POST 
 Reset: Set a new password using a token or OTP.
 <code>/change-password</code> 
 POST 
 Update: Change password for authenticated user.
 <code>/sso/exchange</code> 
 POST 
 SSO: Exchange a remote site token for a local session.
<h3>1. Login (Generate Token)</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/token</code> 
Description: Authenticate a user and generate a JWT token.
Request: 
 <code>json 
{ 
 "username": "admin", 
 "password": "secret-password" 
}</code>
Response: 
 <code>json 
{ 
 "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9...", 
 "expiration": "2023-10-27T10:00:00+00:00", 
 "expires_in": 3600, 
 "user": { 
 "ID": 1, 
 "user_login": "admin", 
 "user_email": "admin@example.com", 
 "display_name": "Administrator", 
 "roles": ["administrator"] 
 }, 
 "refreshable": true, 
 "jti": "545086b9-450f-488b-a70d-3047d14d1101" 
}</code>
<h3>2. Validate Token</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/token/validate</code> 
Description: Validate if an existing token is valid.
Request: 
 <code>json 
{ 
 "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9..." 
}</code>
Response: 
 <code>json 
{ 
 "valid": true, 
 "data": { 
 "iss": "https://example.com", 
 "iat": 1698393600, 
 "exp": 1698397200, 
 "data": { 
 "ID": 1, 
 "user_login": "admin" 
 } 
 } 
}</code>
<h3>3. Refresh Token</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/token/refresh</code> 
Description: Rotate an expiring token for a fresh one.
Request: 
 <code>json 
{ 
 "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9..." 
}</code>
Response: 
 <code>json 
{ 
 "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.new...", 
 "expiration": "2023-10-27T11:00:00+00:00", 
 "user": { 
 "ID": 1, 
 "user_login": "admin" 
 }, 
 "jti": "new-uuid-v4" 
}</code>
<h3>4. Revoke Token (Logout)</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/token/revoke</code> 
Description: Invalidate a token immediately.
Request: 
 <code>json 
{ 
 "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9..." 
}</code>
Response: 
 <code>json 
{ 
 "message": "Token revoked successfully." 
}</code>
<h3>5. Register User</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/register</code> 
Description: Create a new user account.
Request: 
 <code>json 
{ 
 "username": "johndoe", 
 "email": "john@example.com", 
 "password": "secure-password", 
 "name": "John Doe" 
}</code>
Response: 
 <code>json 
{ 
 "user_id": 45, 
 "user": { 
 "ID": 45, 
 "user_login": "johndoe", 
 "user_email": "john@example.com", 
 "display_name": "John Doe", 
 "roles": ["subscriber"] 
 }, 
 "token_response": { 
 "token": "eyJ0eXAiOiJKV1QiLCJhbGciOi...", 
 "expiration": "2023-10-27T10:00:00+00:00" 
 } 
}</code>
<h3>6. User Profile (Login Extended)</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/login</code> 
Description: Alternative login endpoint that returns cleaner profile structure.
Request: 
 <code>json 
{ 
 "username": "admin", 
 "password": "secret-password" 
}</code>
Response: 
 <code>json 
{ 
 "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9...", 
 "expiration": "2023-10-27T10:00:00+00:00", 
 "user": { 
 "ID": 1, 
 "user_login": "admin", 
 "user_email": "admin@example.com", 
 "display_name": "Administrator", 
 "roles": ["administrator"] 
 } 
}</code>
<h3>7. Forgot Password</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/forgot-password</code> 
Description: Initiate password recovery. Note: <code>delivery</code> can be <code>link</code> or <code>otp</code>.
Request: 
 <code>json 
{ 
 "login": "admin@example.com", 
 "delivery": "link" 
}</code>
Response: 
 <code>json 
{ 
 "message": "Password reset email sent." 
}</code>
<h3>8. Reset Password</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/reset-password</code> 
Description: Reset password using the token sent via email or OTP.
Request (Link method): 
 <code>json 
{ 
 "login": "admin@example.com", 
 "password": "new-secure-password", 
 "token": "generated-reset-key" 
}</code>
Response: 
 <code>json 
{ 
 "message": "Password updated successfully." 
}</code>
<h3>9. Change Password</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/change-password</code> 
Description: Change password for currently authenticated user. Requires <code>Authorization</code> header.
Headers: 
 Authorization: Bearer 
Request: 
 <code>json 
{ 
 "current_password": "old-password", 
 "new_password": "new-secure-password" 
}</code>
Response: 
 <code>json 
{ 
 "message": "Password changed successfully. Please login again." 
}</code>
<h3>10. SSO Token Exchange</h3>
Endpoint: <code>POST /wp-json/headlesskey/v1/sso/exchange</code> 
Description: Securely exchange a token from a connected remote site for a local authentication session. This powers the distributed Single Sign-On network.
Request: 
 <code>json 
{ 
 "site_key": "remote-site-id", 
 "token": "remote-jwt-token", 
 "signature": "hmac-sha256-signature" 
}</code>
Response: 
Returns a standard Login response (Token + User Data) if the signature is valid.

HeadlessKey – JWT Auth

A complete authentication solution for Headless WordPress applications using JWT, supporting Registration, SSO, RBAC, and advanced Security features.

miniorange

WordPress REST API endpoints are open and unsecured by default which can be used to access your site data. Secure WordPress APIs from unauthorized users with our <a href="https://plugins.miniorange.com/wordpress-rest-api-authentication" rel="nofollow ugc">JWT Authentication for WP REST APIs plugin</a>.
Our plugin offers below authentication methods to Protect WP REST API endpoints: 
– <a href="https://plugins.miniorange.com/wordpress-rest-api-jwt-authentication-method" rel="nofollow ugc">JWT Authentication</a> 
– <a href="https://plugins.miniorange.com/wordpress-rest-api-basic-authentication-method" rel="nofollow ugc">Basic Authentication</a> 
– <a href="https://plugins.miniorange.com/rest-api-key-authentication-method" rel="nofollow ugc">API Key Authentication</a> 
– <a href="https://plugins.miniorange.com/wordpress-rest-api-oauth-2-0-authentication-method" rel="nofollow ugc">OAuth 2.0 Authentication</a> 
– External Token based Authentication 2.0/OIDC/JWT/<a href="https://firebase.google.com/docs/auth/admin/create-custom-tokens" rel="nofollow ugc">Firebase</a> provider’s token authentication methods.
You can authenticate default WordPress endpoints and custom-developed REST endpoints and third-party plugin REST API endpoints like that of <a href="https://wordpress.org/plugins/woocommerce/" rel="ugc">Woocommerce</a>, <a href="https://www.learndash.com/" rel="nofollow ugc">Learndash</a>, <a href="https://wordpress.org/plugins/buddypress/" rel="ugc">Buddypress</a>, <a href="https://www.gravityforms.com/" rel="nofollow ugc">Gravity Forms</a>, <a href="https://wordpress.org/plugins/cart-rest-api-for-woocommerce/" rel="ugc">CoCart</a>, etc.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/IsyKI7eEV-I?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&start=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h3>WP REST API Authentication Methods in our plugin</h3>
<ul>
<li><a href="https://plugins.miniorange.com/wordpress-rest-api-jwt-authentication-method#step_a1" rel="nofollow ugc">JWT Authentication</a> 
Provides an endpoint where you can pass the user credentials, and it will generate a JWT (JSON Web Token), which you can use to access the WordPress REST APIs accordingly. 
Additionally, to maintain a seamless user experience without frequent logins needed due to token expiry, you can use our Refresh and Revoke token mechanisms feature. 
When the access token expires, instead of forcing the user to log in again, the client can request a new access token using a valid refresh token.</li>
<li><a href="https://plugins.miniorange.com/rest-api-key-authentication-method#step_a" rel="nofollow ugc">API Key Authentication</a></li>
<li><a href="https://plugins.miniorange.com/wordpress-rest-api-basic-authentication-method" rel="nofollow ugc">Basic Authentication</a>: 
 – 1. Username: Password 
 – 2. Client-ID: Client-Secret</li>
<li><a href="https://plugins.miniorange.com/wordpress-rest-api-oauth-2-0-authentication-method#step_a" rel="nofollow ugc">OAuth 2.0 Authentication</a> 
 – 1. Password Grant 
 – 2. Client Credentials Grant</li>
<li><a href="https://plugins.miniorange.com/wordpress-rest-api-authentication-using-third-party-provider#step_a" rel="nofollow ugc">Third Party Provider Authentication</a></li>
</ul>
<h3>Following are some of the integrations that are possible with WP REST API Authentication:</h3>
<ul>
<li>Learndash API Authentication</li>
<li>Custom Built REST API Endpoints Authentication</li>
<li>BuddyPress API Authentication</li>
<li>WooCommerce API Authentication</li>
<li>Gravity Form API Authentication</li>
<li>External/Third-party plugin API endpoints integration in WordPress</li>
</ul>
You can also disable the WP REST APIs with our plugin such that no one can make API calls to your WordPress REST API endpoints.Our plugin also provides Refresh and Revoke Token that can be used to improve the API security.
<h3>Benefits of Refresh Token</h3>
<ul>
<li>Enhances security by keeping access tokens short-lived.</li>
<li>Improves user experience with uninterrupted sessions.</li>
<li>Reduces login frequency.</li>
</ul>
<h3>Benefits of Revoke Token</h3>
<ul>
<li>Protects against token misuse if a device is lost or compromised.</li>
<li>Enables admin-triggered logouts or session control.</li>
<li>Useful for complying with stricter session policies.</li>
</ul>
With this plugin, the user is allowed to access your site’s resources only after successful WP REST API authentication. JWT Authentication for WP REST APIs plugin will make your WordPress endpoints secure from unauthorized access.
<h3>Plugin Feature List</h3>
<h3>FREE PLAN</h3>
<ul>
<li>Authenticate only default core WordPress REST API endpoints.</li>
<li>Basic Authentication with username and password.</li>
<li>JWT Authentication (JSON Web Token Authentication).</li>
<li>Enable Selective API protection.</li>
<li>Restrict non-logged-in users to access REST API endpoints.</li>
<li>Disable WP REST APIs</li>
</ul>
<h3>PREMIUM PLAN</h3>
<ul>
<li>Authenticate all REST API endpoints (Default WP, Custom APIs,Third-Party plugins)</li>
<li>JWT Token Authentication (JSON Web Token Authentication)</li>
<li>Login, Refresh and Revoke token endpoints for token management</li>
<li>API Key Authentication</li>
<li>Basic Authentication (username/password and email/password)</li>
<li>OAuth 2.0 Authentication</li>
<li>Universal API key and User-specific API key for authentication</li>
<li>Selective API protection.</li>
<li>Disable WP REST APIs</li>
<li>Time-based token expiry</li>
<li>Role-based WP REST API authentication</li>
<li>Custom Header support rather than just Authorization to increase security.</li>
<li>Create users in WordPress based on third-party provider access tokens (JWT tokens) authentication.</li>
</ul>
<h3>Privacy</h3>
This plugin does not store any user data.

JWT Authentication for WP REST APIs

This was the plugin that I was looking for. It is just plug and play!

Great plugin, does as it says!


Great support from the MiniOrange team! Atul and Vidushi are very helpful and lightning fast to respond.


Great Support

Secure and protect WordPress REST API from unauthorized access using JWT token, Basic Authentication, API Key, OAuth 2, or external token.

HeadlessKey – JWT Auth vs JWT Authentication for WP REST APIs