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.

jeremyjsimmons

TWL SSO is a secure single sign-on plugin for WordPress that enables seamless authentication using RS256 JWT tokens from an external SSO application. 
This plugin provides login security features and is designed for allowing Twelve Legs Marketing centralized authentication management.
<h4>Key Features</h4>
<ul>
<li>Single Sign In: Agency employees can log into websites they manage from a central dashboard.</li>
<li>Just-in-Time User Provisioning: Automatic user creation and role assignment</li>
<li>JWT Validation: Full RS256 signature verification with JWKS endpoint integration</li>
<li>Key Rotation: Support key rotation through JWKS endpoint</li>
<li>Role Management: Flexible role assignment from JWT claims</li>
<li>Referrer Validation: Enhanced security through referrer validation</li>
<li>Audience Validation: Ensures tokens are valid for the specific WordPress site</li>
<li>Token Expiration: Built-in token expiration and clock skew tolerance</li>
<li>Email Validation: Comprehensive email validation with optional allowlist</li>
<li>Caching: JWKS caching for improved performance</li>
</ul>
<h4>Security Features</h4>
<ul>
<li>Referrer validation to prevent unauthorized access</li>
<li>JWT signature verification using public key cryptography</li>
<li>Issuer validation to ensure tokens come from trusted sources</li>
<li>Audience validation to prevent token reuse across sites</li>
<li>Token expiration validation with configurable leeway</li>
<li>Email format validation and filtering via hook</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li>WordPress installations managed centrally by agency</li>
<li>Organization using Google for external identity provider</li>
</ul>
<h3>Usage</h3>
<h4>Authentication Flow</h4>
<ol>
<li>User clicks login link from SSO application sso.twelvelegsmarketing.com</li>
<li>SSO application redirects to WordPress with JWT token: <code>/wp-login.php?action=twl_sso&token=JWT_TOKEN</code></li>
<li>Plugin validates the JWT token signature and claims</li>
<li>Plugin extracts user information from JWT claims</li>
<li>Plugin creates or retrieves WordPress user</li>
<li>Plugin assigns appropriate role based on JWT claims</li>
<li>User is logged into WordPress</li>
</ol>
<h4>JWT Claims</h4>
The plugin expects the following JWT claims:
<ul>
<li><code>email</code> or <code>sub</code>: User’s email address</li>
<li><code>iss</code>: Issuer (must match allowed issuers)</li>
<li><code>aud</code>: Audience (must match WordPress site URL)</li>
<li><code>exp</code>: Expiration time</li>
<li><code>nbf</code>: Not before time (optional)</li>
<li><code>wp_role</code>: WordPress role to assign (optional)</li>
<li><code>name</code>: User’s display name (optional)</li>
<li><code>given_name</code>: User’s first name (optional)</li>
<li><code>family_name</code>: User’s last name (optional)</li>
</ul>
<h4>Configuration</h4>
The plugin automatically configures itself based on the WordPress environment:
<ul>
<li>Production: Only allows <code>https://sso.twelvelegsmarketing.com</code> as issuer</li>
<li>Development/Staging: Also allows <code>https://localhost:8443</code> as issuer</li>
</ul>
<h4>Customization</h4>
You can customize the plugin behavior using WordPress filters:
<ul>
<li><code>twl_sso_allow_email</code>: Filter to control which email addresses are allowed</li>
<li><code>twl_sso_allowed_roles</code>: Filter to control which roles can be assigned</li>
<li><code>twl_sso_allowed_issuers</code>: Filter to control which issuers are allowed</li>
</ul>
<h3>Support</h3>
For support, please contact Twelve Legs Marketing at https://twelvelegsmarketing.com
<h3>Privacy Policy</h3>
This plugin does not collect, store, or transmit any personal data. All authentication is handled through secure JWT tokens from your configured SSO provider.

Twelve Legs Marketing SSO

Single sign-on plugin for WordPress that accepts RS256 JWTs from the TWL SSO application for secure authentication.

HeadlessKey – JWT Auth vs Twelve Legs Marketing SSO