jeremyjsimmons

<p>TWL SSO is a secure single sign-on plugin for WordPress that enables seamless authentication using RS256 JWT tokens from an external SSO application.<br />
This plugin provides login security features and is designed for allowing Twelve Legs Marketing centralized authentication management.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Single Sign In</strong>: Agency employees can log into websites they manage from a central dashboard.</li>
<li><strong>Just-in-Time User Provisioning</strong>: Automatic user creation and role assignment</li>
<li><strong>JWT Validation</strong>: Full RS256 signature verification with JWKS endpoint integration</li>
<li><strong>Key Rotation</strong>: Support key rotation through JWKS endpoint</li>
<li><strong>Role Management</strong>: Flexible role assignment from JWT claims</li>
<li><strong>Referrer Validation</strong>: Enhanced security through referrer validation</li>
<li><strong>Audience Validation</strong>: Ensures tokens are valid for the specific WordPress site</li>
<li><strong>Token Expiration</strong>: Built-in token expiration and clock skew tolerance</li>
<li><strong>Email Validation</strong>: Comprehensive email validation with optional allowlist</li>
<li><strong>Caching</strong>: 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>
<p>The plugin expects the following JWT claims:</p>
<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>
<p>The plugin automatically configures itself based on the WordPress environment:</p>
<ul>
<li><strong>Production</strong>: Only allows <code>https://sso.twelvelegsmarketing.com</code> as issuer</li>
<li><strong>Development/Staging</strong>: Also allows <code>https://localhost:8443</code> as issuer</li>
</ul>
<h4>Customization</h4>
<p>You can customize the plugin behavior using WordPress filters:</p>
<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>
<p>For support, please contact Twelve Legs Marketing at https://twelvelegsmarketing.com</p>
<h3>Privacy Policy</h3>
<p>This plugin does not collect, store, or transmit any personal data. All authentication is handled through secure JWT tokens from your configured SSO provider.</p>


Twelve Legs Marketing SSO

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

michielve

<p>The API Bearer Auth plugin enables authentication for the REST API by using JWT access an refresh tokens. After the user logs in, the access and refresh tokens are returned and can be used for the next requests. Issued tokens can be revoked from within the users admin screen. See below for the endpoints.</p>
<p><strong>Note that after activating this plugin, all REST API endpoints will need to be authenticated, unless the endpoint is whitelisted in the <code>api_bearer_auth_unauthenticated_urls</code> filter (see FAQ for how to use this filter).</strong></p>
<h4>JWT</h4>
<p>Access tokens can be formatted as JWT tokens. For this to work, you first have to create a secret and add it to the wp-config.php file. If you don’t do this, access tokens will work also, but are just random strings. To create a random secret key, you can do for example:</p>
<pre><code>base64_encode(openssl_random_pseudo_bytes(64));
</code></pre>
<p>And then add the result to wp-config:</p>
<pre><code>define('API_BEARER_JWT_SECRET', 'mysecretkey');
</code></pre>
<p>If you have problems, you can verify your JWT tokens at: <a href="https://jwt.io/" rel="nofollow ugc">https://jwt.io/</a></p>
<h4>Revoke tokens</h4>
<p>This plugin adds a column to the users table in de admin where you can see when a token expires. You can also revoke tokens by selection the “Revoke API tokens” from the bulk actions select box.</p>
<h4>API endpoints</h4>
<p>Note that all endpoints <strong>expect JSON in the POST body</strong>.</p>
<p><strong>Login</strong></p>
<p>Endpoint:</p>
<pre><code>POST /api-bearer-auth/v1/login
</code></pre>
<p>Request body:</p>
<p><strong>Note: <code>client_name</code> is optional. But if you use it, make sure to use it as well for the refresh call!</strong></p>
<pre><code>{"username": "my_username", "password": "my_password", "client_name": "my_app"}
</code></pre>
<p>Response:</p>
<pre><code>{
  "wp_user": {
    "data": {
      "ID": 1,
      "user_login": "your_user_login",
      // other default WordPress user fields
    }
  },
  "access_token": "your_access_token",
  "expires_in": 86400, // number of seconds
  "refresh_token": "your_refresh_token"
}
</code></pre>
<p>Make sure to save the access and refresh token!</p>
<p><strong>Refresh access token</strong></p>
<p>Endpoint:</p>
<pre><code>POST /api-bearer-auth/v1/tokens/refresh
</code></pre>
<p>Request body:</p>
<p><strong>Note: <code>client_name</code> is optional. But if you did use it for the login call, make sure to use it here as well!</strong></p>
<pre><code>{"token": "your_refresh_token", "client_name": "my_app"}
</code></pre>
<p>Response success:</p>
<pre><code>{
  "access_token": "your_new_access_token",
  "expires_in": 86400
}
</code></pre>
<p>Response when sending a wrong refresh token is a 401:</p>
<pre><code>{
  "code": "api_api_bearer_auth_error_invalid_token",
  "message": "Invalid token.",
  "data": {
    "status": 401
  }
}
</code></pre>
<p><strong>Do a request</strong></p>
<p>After you have the access token, you can make requests to authenticated endpoints  with an Authorization header like this:</p>
<pre><code>Authorization: Bearer <your_access_token>
</code></pre>
<p>Note that Apache sometimes strips out the Authorization header. If this is the case, make sure to add this to the .htaccess file:</p>
<pre><code>RewriteCond %{HTTP:Authorization} ^(.*)
# Don't know why, but some need the line below instead of the RewriteRule line
# SetEnvIf Authorization .+ HTTP_AUTHORIZATION=$0
RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
</code></pre>
<p>If you are not logged in or you send an invalid access token, you get a 401 response:</p>
<pre><code>{
  "code": "api_bearer_auth_not_logged_in",
  "message": "You are not logged in.",
  "data": {
    "status": 401
  }
}
</code></pre>
<h3>Important update</h3>
<p><strong>Update immediately if you’re using a version below 20200807. Before this version all access tokens were updated when calling the refresh callback.</strong></p>
<p>If you are affected by this the fastest solution is to execute this query:</p>
<pre><code>update wp_user_tokens set access_token_valid = NOW();
</code></pre>
<p>This will invalidate all access tokens. This means that all users need to refresh their access token and will get a new access token and a unique one this time.</p>
<p>A big thank to @harchvertelol for reporting this and suggesting the fix as well!</p>


API Bearer Auth

The plugin is refreshingly simple in its purpose and it does it perfectly. I could use it to login and use my API via JWT Auth in seconds! Thanks!

Perfectly simple

I love how simple the plugin is. Just need to install, read docs and follow in 5 mins.

Thank you!

Simple

Access and refresh tokens based authentication plugin for the REST API.

Twelve Legs Marketing SSO vs API Bearer Auth