miniOrange

<p>The <strong><a href="https://plugins.miniorange.com/wordpress-login-using-jwt-single-sign-on-sso" rel="nofollow ugc">WordPress Login and Register using JWT plugin</a></strong> allows you to <strong>log in (Single Sign-On)</strong> into your WordPress application using the <strong>JWT token(JSON Web token)</strong> obtained from any other WordPress site or other applications/platforms including mobile applications. This helps users perform <strong>autologin to WordPress</strong> and <strong>synchronize user sessions</strong> without the need to log in again.</p>
<p>|<a href="https://plugins.miniorange.com/wordpress-login-using-jwt-single-sign-on-sso" rel="nofollow ugc"> Features </a>| <a href="https://plugins.miniorange.com/wordpress-single-sign-on-using-jwt-token" rel="nofollow ugc"> WordPress JWT Login Setup Guide </a>|<a href="https://www.youtube.com/playlist?list=PL2vweZ-PcNpevdcrVhs_dQ3qOxc0102wI" rel="nofollow ugc"> Videos </a>|</p>
<p><strong>WORDPRESS SINGLE SIGN-ON / SSO ( LOGIN INTO WORDPRESS )</strong><br />
<strong>WordPress Single Sign-On SSO</strong> also simply called <strong>WordPress SSO</strong> allows you to login into WordPress using the credentials of other platforms. So, the user will just use a single set of credentials to log in to multiple applications.</p>
<p><strong>WordPress Single Sign-On / SSO using JWT(JSON Web Token)</strong><br />
<strong>WordPress Single Sign-On (SSO) with JWT</strong> allows you to log into the WordPress site using the user-based JWT token obtained externally when the user authenticates for the first time in any connected external application.<br />
The JWT token authentication is the most popular way of authentication nowadays as it is a secure and lightweight protocol. The JWT token can be obtained either when a user logs into other platforms via <strong><a href="https://oauth.net/" rel="nofollow ugc">OAuth</a>/<a href="https://openid.net/connect/" rel="nofollow ugc">OpenID Connect</a></strong> protocol or can be created explicitly using the user information and secure algorithms.<br />
With this plugin, you can easily use the user-based JWT token to log a user in rather than asking them to authenticate again.</p>
<p><em>Let’s take an example</em> – If you have a WordPress site and mobile app, now if you are logged into the mobile app, now if you try to access the WordPress site, then to access the particular content, the WordPress site will ask for login again and which is not feasible, so with the JWT SSO (JWT Single Sign-On), you can create the JWT token for the user who is already logged into the mobile app and then on accessing the WordPress site, you can pass that JWT token in the request, using which the same user can authenticate and autologin to the WordPress site and hence won’t need to enter the credentials again.</p>
<p>It supports possibly all kinds of <strong>JWT tokens (access-token/id-token)</strong> obtained from <strong>OAuth/OpenID Connect</strong> providers like <strong>AWS Cognito</strong>, <strong>Microsoft Azure AD</strong>, <strong>Azure B2C</strong>, <strong>Okta</strong>, <strong>Keycloak</strong>, <strong>ADFS</strong>, <strong>Google</strong>, <strong>Facebook</strong>, <strong>Apple</strong>, <strong>Discord</strong> and popular applications like <strong>Firebase</strong>.</p>
<p>WordPress login using the JWT also called <strong>JWT SSO (Single Sign-On)</strong> can be done from other platforms and applications including mobile apps (android or IOS), an app built with other programming languages like <strong>.NET</strong>, <strong>JAVA</strong>, <strong>PHP</strong>, <strong>JS</strong> etc.</p>
<h3>Major functionalities</h3>
<p><strong>WordPress Login Endpoint to create user-based JWT token</strong><br />
Plugin provides the following API endpoint, which can be used to authenticate WordPress users and returns a user-based JWT which can be used to create login sessions in WordPress and other external applications.</p>
<pre><code>/wp-json/api/v1/mo-jwt
</code></pre>
<p><strong>WordPress Login using JWT</strong><br />
This feature provides a way to auto-login users in WordPress using JWT obtained in a very secure way either via passing JWT token in the URL as a parameter, in the request header or shared via secured cookies.</p>
<p><strong>WordPress user register API endpoint to create users in WordPress using API</strong><br />
This feature provides the following API endpoint to create users in WordPress in an easy way and on successful user registration, you will receive a JWT token in the response which can be used further for user login and WordPress REST API authorization.</p>
<pre><code>wp-json/api/v1/mo-jwt-register
</code></pre>
<p><strong>Delete/Remove users from WordPress using the user-based JWT token (JSON Web Token)</strong><br />
This feature provides an API endpoint using which you can pass the JWT token and can easily delete the user and revoke access.</p>
<pre><code>wp-json/api/v1/mo-jwt-delete
</code></pre>
<p>More details for the plugin setup can be checked from <strong><a href="https://plugins.miniorange.com/wordpress-single-sign-on-using-jwt-token" rel="nofollow ugc">here</a></strong>.</p>
<h3>USE CASES</h3>
<ul>
<li>
<p><strong>Login to External applications using WordPress credentials</strong><br />
If you are looking to authenticate your WordPress users to log in to external applications, then our plugin provides a login API endpoint using which you can easily authenticate WordPress users and can log in the users to those applications.</p>
</li>
<li>
<p><strong>Single Sign-On Users using the JWT token provided by OAuth/OpenID providers</strong><br />
This WordPress login and register using the JWT plugin supports the WordPress Single Sign On (WordPress SSO) or WordPress login using the user-based JWT token (id-token/access-token) provided by the external OAuth/OpenID Connect providers (like Microsoft Azure AD, Azure B2C, AWS Cognito, Keycloak, Okta, ADFS, Google, Facebook, Apple, Discord and many more..) on login in some other sites/applications using their credentials.<br />
So, the user just needs to log in once on any other sites/platforms and a JWT token will be provided by these providers for those users will then be used further with security to autologin in other platforms.</p>
</li>
</ul>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/RR0o80hGvfU?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<ul>
<li><strong>Automatic WordPress login and site access from mobile app web view | Synchronize WordPress session in the mobile app web view</strong><br />
Suppose you have a mobile application and want to allow users to access their WordPress site content in the mobile app web view which requires a login so asking the users to enter the credentials again won’t be a good user experience. So, our JWT login plugin provides a solution to you in which the user session from the mobile app can be synchronized with the WordPress site and the user can seamlessly access the WordPress site using the user-based JWT token without the need for a WordPress login again.</li>
</ul>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/0QPIjelCWvk?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<ul>
<li><strong>Automatic session synchronization between WordPress and other applications built on React, Node, Next JS, Flutter, Angular, Java, PHP, and C# ….</strong><br />
Suppose you have a WordPress site connected to any external application built on any framework, then if you want a feature that if a user is logged in to any one application, should be automatically logged in to another as well. This can be easily achieved using the secure JWT.</li>
</ul>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/OMH_FY-xh8Q?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<ul>
<li><strong>Session sharing between WordPress and other applications sharing the same subdomain (hosted on the same domain)</strong><br />
Suppose you have a WordPress site and other applications hosted on the same subdomain, such that if the user logs in to any one application, then can be auto-logged into other connected applications on that domain using secure cookie-based JWT token sharing.<br />
an pass the new user details like username, email, name and password(optional), role etc. in the request body and on successful response, your user will get created and the corresponding user-based JWT will be received and the appropriate error response will be returned on the failure.</li>
</ul>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/Lr9spH2PPeY?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent&listType=playlist&list=PL2vweZ-PcNpevdcrVhs_dQ3qOxc0102wI" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<ul>
<li><strong>Sync user login sessions between multiple platforms (Session sharing)</strong><br />
If you have a WordPress site and other applications sharing the same subdomain and you want the feature in which if a user logged into one site (WordPress or another) and on accessing the other site in the same browser, then that user should get logged in automatically (user session to be synchronized). So, this feature is possible to have with our plugin’s JWT cookie-based session-sharing feature.</li>
</ul>
<h3>Features</h3>
<p>FREE PLAN</p>
<p><em>Create JWT feature</em></p>
<ul>
<li><strong>Login API endpoint</strong> to authenticate WordPress users based on username/email and password</li>
<li>Supports the JWT token generation using the <strong>HS256 signing algorithm</strong>.</li>
<li>JWT token signing with randomly generated secret signing key.</li>
<li>Default JWT <strong>token expiration</strong> is 60 minutes.</li>
</ul>
<p><em>User Registration feature</em></p>
<ul>
<li>Provide an API endpoint for user registration with the default subscriber role.</li>
<li>Provide a user-based JWT token in the success response.</li>
<li>No Extra Security key for user registration API.</li>
</ul>
<p><em>User Deletion feature</em></p>
<ul>
<li>Provide an API endpoint for user deletion with JWT token validation using the HS256 signing algorithm.</li>
<li>No Extra Security key for user deletion API.</li>
</ul>
<p><em>User login feature</em></p>
<ul>
<li>Allows WordPress login (SSO) using a user-based JWT token with HS256 signing created using the plugin’s Create JWT feature.</li>
<li>Retrieve the JWT token from the URL parameter to allow auto-login.</li>
<li>Auto redirection on login to the homepage or on the same page/URL from where the autologin is initiated.</li>
<li>Default Subscriber role is assigned on login using JWT.</li>
</ul>
<p>PREMIUM PLAN</p>
<p><em>Create JWT feature</em></p>
<ul>
<li>Supports JWT token generation using <strong>HS256</strong> and a securer <strong>RS256 signing algorithm</strong>.</li>
<li>JWT token signing with a <strong>custom secret signing key or certificate</strong>.</li>
<li>Custom token expiration to expire the token as per your requirement to improvise security.</li>
<li>Custom JWT token decryption key.</li>
<li>Revoke and invalidate existing user JWT token whenever a new JWT token is generated for a user.</li>
</ul>
<p><em>User Registration feature</em></p>
<ul>
<li>Provide an API endpoint for user registration with a custom role.</li>
<li>Provide a user-based JWT token in the success response.</li>
<li>Extra Security key for user registration API endpoint.</li>
</ul>
<p><em>User Deletion feature</em></p>
<ul>
<li>Provide an API endpoint for user deletion with JWT token validation using the HS256 signing algorithm.</li>
<li>Extra Security key for user deletion API.</li>
</ul>
<p><em>User login feature</em></p>
<ul>
<li>Allows WordPress login (SSO) using a user-based JWT with HS256 signing created either using plugins create JWT feature or a JWT token obtained from an external source.</li>
<li>Allows WordPress login using a user-based JWT with RS256 signing validation.</li>
<li>Allows WordPress login using a user-based JWT with <strong>JWKS token validation</strong> support.</li>
<li>Allows WordPress login using a user-based JWT obtained from an external <strong>OAuth/OpenID Connect</strong> provider.</li>
<li>Retrieve the JWT token from the <strong>URL parameter</strong>, <strong>request header</strong> and <strong>cookie</strong> to allow auto-login between platforms.</li>
<li><strong>Auto redirection</strong> on login to the homepage or on the same page/URL from where the autologin is initiated.</li>
<li>Auto redirection on login to any custom URL.</li>
<li>User <strong>Attribute/Profile</strong> mapping on SSO login.</li>
<li>Option to assign any WordPress role rather than default subscriber on SSO login.</li>
<li><strong>Automatic role and group Mapping</strong> to the user who performs SSO using a JWT token.</li>
<li><strong>SSO Login Audit feature</strong> to track the users who perform login using the JWT token.</li>
<li>Add-On to <strong>share the user session to other applications</strong> using the JWT token stored in the cookie</li>
</ul>
<h3>Other Related Integrations</h3>
<p><strong><a href="https://wordpress.org/plugins/miniorange-login-with-eve-online-google-facebook/" rel="ugc">OAuth Single Sign On – SSO (OAuth Client)</a></strong> – This plugin allows Single Sign On – SSO login in your WordPress site using external OAuth 2.0, OpenID Connect Providers</p>
<p><strong><a href="https://wordpress.org/plugins/miniorange-api-20-single-sign-on/" rel="ugc">api Single Sign On – SSO Login</a></strong> – This plugin allows Single Sign On – SSO login in your WordPress site using external api, WS-FED Providers</p>
<p><strong><a href="https://wordpress.org/plugins/wp-rest-api-authentication/" rel="ugc">WordPress REST API Authentication</a></strong> – This plugin protects your WordPress REST API endpoints from unauthorized access using secure <strong>OAuth 2.0</strong>, <strong>JWT authentication</strong>, <strong>Basic authentication</strong>, <strong>Bearer API Key token</strong> and even more.</p>
<h3>Privacy</h3>
<p>This plugin does not store any user data. This plugin uses login.xecurify.com for registration as miniOrange uses login.xecurify.com if the user chooses to register and upgrade to premium. If the user does not want to register then he can continue using the free plugin. (Link to the privacy policy –  https://www.miniorange.com/privacy-policy.pdf )</p>


WP Login and Register using JWT

WordPress login (WordPress Single Sign-On) using JWT token obtained from other WordPress sites or any other application. Synchronize user sessions bet …

Sayan Dey

<p>Extends the WordPress REST API using JSON Web Tokens for robust authentication and authorization.</p>
<p>JSON Web Token (JWT) is an open standard (<a href="https://tools.ietf.org/html/rfc7519" rel="nofollow ugc">RFC 7519</a>) that defines a compact and self-contained way for securely transmitting information between two parties.</p>
<p>It provides a secure and reliable way to access and manage WordPress data from external applications, making it ideal for building headless CMS solutions.</p>
<ul>
<li>Support & question: <a href="https://wordpress.org/support/plugin/simple-jwt-auth/" rel="ugc">WordPress support forum</a></li>
<li>Reporting plugin’s bug: <a href="https://github.com/sayandey18/simple-jwt-auth/issues" rel="nofollow ugc">GitHub issues tracker</a></li>
</ul>
<p><strong>Plugins GitHub Repo</strong> https://github.com/sayandey18/simple-jwt-auth</p>
<h3>Enable PHP HTTP Authorization Header</h3>
<p>HTTP Authorization is a mechanism that allows clients to provide credentials to servers, thereby gaining access to protected resources. This is typically achieved by sending a special header, the Authorization header, in the HTTP request.</p>
<h4>Shared Hosts</h4>
<p>Most shared hosts have disabled the <strong>HTTP Authorization Header</strong> by default.</p>
<p>To enable this option you’ll need to edit your <strong>.htaccess</strong> file by adding the following:</p>
<pre><code>RewriteEngine on
RewriteCond %{HTTP:Authorization} ^(.*)
RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
</code></pre>
<h4>WPEngine</h4>
<p>To enable this option you’ll need to edit your .htaccess file adding the follow:</p>
<pre><code>SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
</code></pre>
<h3>Configuration</h3>
<p>Simple JWT Auth plugin needs a <strong>Signing Key</strong> to encrypt and decrypt the <strong>secret key</strong>, <strong>private key</strong>, and <strong>public key</strong>. This signing key must be exact 32 charecter long and never be revealed.</p>
<p>To add the <strong>signing key</strong> edit your <code>wp-config.php</code> file and add a new constant called <strong>SIMPLE_JWT_AUTH_ENCRYPT_KEY</strong></p>
<pre><code>define( 'SIMPLE_JWT_AUTH_ENCRYPT_KEY', 'your-32-char-signing-key' );
</code></pre>
<p>Generate a 32 charecter key from here: <a href="https://string-gen.netlify.app" rel="nofollow ugc">https://string-gen.netlify.app</a></p>
<p>Here is the sample response if the encryption key is not configured in wp-config.php file.</p>
<pre><code>{
    "code": "simplejwt_bad_encryption_key",
    "message": "Encryption key is not configured properly.",
    "data": {
        "status": 403
    }
}
</code></pre>
<h3>REST Endpoints</h3>
<p>When the plugin is activated, a new namespace is added.</p>
<pre><code>/auth/v1
</code></pre>
<p>Also, two new endpoints are added to this namespace.</p>
<pre><code>*/wp-json/auth/v1/token          | POST
*/wp-json/auth/v1/token/validate | POST
</code></pre>
<h3>Requesting/Generating Token</h3>
<p>To generate a new token, submit a POST request to this endpoint. With <code>username</code> and <code>password</code> as the parameters.</p>
<p>It will validates the user credentials, and returns success response including a token if the authentication is correct or returns an error response if the authentication is failed.</p>
<pre><code>curl --location 'https://example.com/wp-json/auth/v1/token' \
--header 'Content-Type: application/json' \
--data-raw '{
    "username": "wordpress_username",
    "password": "wordpress_password"
}'
</code></pre>
<h4>Sample of success response</h4>
<pre><code>{
    "code": "simplejwt_auth_credential",
    "message": "Token created successfully",
    "data": {
        "status": 200,
        "id": "2",
        "email": "sayandey@outlook.com",
        "nicename": "sayan_dey",
        "display_name": "Sayan Dey",
        "token": "eyJ0eXAiOiJKV1QiLCJhbGciO........."
    }
}
</code></pre>
<h4>Sample of error response</h4>
<pre><code>{
    "code": "simplejwt_invalid_username",
    "message": "Error: The username admin_user is not registered on this site. If you are unsure of your username, try your email address instead.",
    "data": {
        "status": 403
    }
}
</code></pre>
<p>Once you get the token, you can store it somewhere in your application:</p>
<ul>
<li>using <strong>Cookie</strong> </li>
<li>or using <strong>localstorage</strong> </li>
<li>or using a wrapper like <a href="https://localforage.github.io/localForage/" rel="nofollow ugc">localForage</a> or <a href="https://pouchdb.com/" rel="nofollow ugc">PouchDB</a></li>
<li>or using local database like SQLite</li>
<li>or your choice based on app you develop</li>
</ul>
<p>Then you should pass this token as <em>Bearer Authentication</em> header to every API call.</p>
<pre><code>Authorization: Bearer your-generated-token
</code></pre>
<p>Here is an example to create WordPress post using JWT token authentication.</p>
<pre><code>curl --location 'https://example.com/wp-json/wp/v2/posts' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciO.........' \
--data '{
    "title": "Dummy post through API",
    "content": "Lorem Ipsum is simply dummy text of the printing and typesetting industry.",
    "status": "publish",
    "tags": [
        4,
        5,
        6
    ]
}'
</code></pre>
<p>Plugin’s middleware intercepts every request to the server, checking for the presence of the <strong>Authorization</strong> header. If the header is found, it attempts to decode the JWT token contained within.</p>
<p>Upon successful decoding, the middleware extracts the user information stored in the token and authenticates the user accordingly, ensuring that only authorized requests are processed.</p>
<h3>Validating Token</h3>
<p>This is a helper endpoint to validate a token. You only will need to make a <strong>POST</strong> request sending the Bearer Authorization header.</p>
<pre><code>curl --location --request POST 'https://example.com/wp-json/auth/v1/token/validate' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciO.........'
</code></pre>
<h4>Sample of success response</h4>
<pre><code>{
    "code": "simplejwt_valid_token",
    "message": "Token is valid",
    "data": {
        "status": 200
    }
}
</code></pre>
<h3>REST Errors</h3>
<p>If the token is invalid an error will be returned, here are some samples of errors.</p>
<h4>Invalid Username</h4>
<pre><code>{
    "code": "simplejwt_invalid_username",
    "message": "Error: The username admin is not registered on this site. If you are unsure of your username, try your email address instead.",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Invalid Password</h4>
<pre><code>{
    "code": "simplejwt_incorrect_password",
    "message": "Error: The password you entered for the username tiyasha_das is incorrect. Lost your password?",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Invalid Signature</h4>
<pre><code>{
    "code": "simplejwt_invalid_token",
    "message": "Signature verification failed",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Invalid Token</h4>
<pre><code>{
    "code": "simplejwt_invalid_token",
    "message": "Syntax error, malformed JSON",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Expired Token</h4>
<pre><code>{
    "code": "simplejwt_invalid_token",
    "message": "Expired token",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>No Authorization</h4>
<pre><code>{
    "code": "simplejwt_no_auth_header",
    "message": "Authorization header not found",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Bad Authorization</h4>
<pre><code>{
    "code": "simplejwt_bad_auth_header",
    "message": "Authorization header malformed",
    "data": {
        "status": 400
    }
}
</code></pre>
<h4>Wrong Algorithm Token</h4>
<pre><code>{
    "code": "simplejwt_invalid_token",
    "message": "Incorrect key for this algorithm",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Unsupported Algorithm</h4>
<pre><code>{
    "code": "simplejwt_unsupported_algorithm",
    "message": "Unsupported algorithm see https://tinyurl.com/uf4ns6fm",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Bad Configuration</h4>
<pre><code>{
    "code": "simplejwt_bad_config",
    "message": "JWT is not configured properly, please contact the admin",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Bad Encryption Key</h4>
<pre><code>{
    "code": "simplejwt_bad_encryption_key",
    "message": "Encryption key is not configured properly.",
    "data": {
        "status": 403
    }
}
</code></pre>
<h4>Invalid Encryption Key Length</h4>
<pre><code>{
    "code": "simplejwt_invalid_enckey_length",
    "message": "Encryption key must be exactly 32 characters long",
    "data": {
        "status": 400
    }
}
</code></pre>
<h3>Available Hooks</h3>
<p><strong>Simple JWT Auth</strong> is a developer-friendly plugin. It has various filter hooks available to override the default settings.</p>
<h4>simplejwt_cors_allow_headers</h4>
<p>The <code>simplejwt_cors_allow_headers</code> allows you to modify the available headers when the Cross-Origin Resource Sharing (CORS) support is enabled.</p>
<p>Default value:</p>
<pre><code>'Access-Control-Allow-Headers, Content-Type, Authorization'
</code></pre>
<p>Usage example:</p>
<pre><code>/**
 * Change the allowed CORS headers.
 *
 * @param   string $headers The allowed headers.
 * @return  string The allowed headers.
 */
add_filter("simplejwt_cors_allow_headers", function ($headers) {
    // Modify the headers here.
    return $headers;
});
</code></pre>
<h4>simplejwt_auth_iss</h4>
<p>The <code>simplejwt_auth_iss</code> allows you to change the <a href="https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.1" rel="nofollow ugc"><strong>iss</strong></a> value before the payload is encoded to be a token.</p>
<p>Default value:</p>
<pre><code>get_bloginfo( 'url' );
</code></pre>
<p>Usage example:</p>
<pre><code>/**
 * Change the token issuer.
 *
 * @param   string $iss The token issuer.
 * @return  string The token issuer.
 */
add_filter("simplejwt_auth_iss", function ($iss) {
    // Modify the "iss" here.
    return $iss;
});
</code></pre>
<h4>simplejwt_not_before</h4>
<p>The <code>simplejwt_not_before</code> allows you to change the <a href="https://tools.ietf.org/html/rfc7519#section-4.1.5" rel="nofollow ugc"><strong>nbf</strong></a> value before the payload is encoded to be a token.</p>
<p>Default value:</p>
<pre><code>time();
</code></pre>
<p>Usage example:</p>
<pre><code>/**
 * Change the token's nbf value.
 *
 * @param   int $not_before The default "nbf" value in timestamp.
 * @param   int $issued_at The "iat" value in timestamp.
 * @return  int The "nbf" value.
 */
add_filter(
    "simplejwt_not_before",
    function ($not_before, $issued_at) {
        // Modify the "not_before" here.
        return $not_before;
    },
    10,
    2,
);
</code></pre>
<h4>simplejwt_auth_expire</h4>
<p>The <code>simplejwt_auth_expire</code> allows you to change the value <a href="https://tools.ietf.org/html/rfc7519#section-4.1.4" rel="nofollow ugc"><strong>exp</strong></a> before the payload is encoded to be a token.</p>
<p>Default value:</p>
<pre><code>time() + ( DAY_IN_SECONDS * 7 )
</code></pre>
<p>Usage example:</p>
<pre><code>/**
 * Change the token's expire value.
 *
 * @param   int $expire The default "exp" value in timestamp.
 * @param   int $issued_at The "iat" value in timestamp.
 * @return  int The "nbf" value.
 */
add_filter(
    "simplejwt_auth_expire",
    function ($expire, $issued_at) {
        // Modify the "expire" here.
        return $expire;
    },
    10,
    2,
);
</code></pre>
<h4>simplejwt_payload_before_sign</h4>
<p>The <code>simplejwt_payload_before_sign</code> allows you to modify all the payload data before being encoded and signed.</p>
<p>Default value:</p>
<pre><code>$payload = [
    "iss" => $this->simplejwt_get_iss(),
    "iat" => $issued_at,
    "nbf" => $not_before,
    "exp" => $expire,
    "data" => [
        "user" => [
            "id" => $user->data->ID,
        ],
    ],
];
</code></pre>
<p>Usage example:</p>
<pre><code>/**
 * Modify the payload data before being encoded & signed.
 *
 * @param   array $payload The default payload
 * @param   WP_User $user The authenticated user.
 * @return  array The payloads data.
 */
add_filter(
    "simplejwt_payload_before_sign",
    function ($payload, $user) {
        // Modify the payload here.
        return $payload;
    },
    10,
    2,
);
</code></pre>
<h4>simplejwt_token_before_dispatch</h4>
<p>The <code>simplejwt_token_before_dispatch</code> allows you to modify the token response before to dispatch it to the client.</p>
<p>Default value:</p>
<pre><code>$data = new WP_REST_Response(
    [
        "code" => "simplejwt_auth_credential",
        "message" => JWTNotice::get_notice("auth_credential"),
        "data" => [
            "status" => 200,
            "id" => $user->data->ID,
            "email" => $user->data->user_email,
            "nicename" => $user->data->user_nicename,
            "display_name" => $user->data->display_name,
            "token" => $token,
        ],
    ],
    200,
);
</code></pre>
<p>Usage example:</p>
<pre><code>/**
 * Modify the JWT response before dispatch.
 *
 * @param   WP_REST_Response $data The token response data.
 * @param   WP_User $user The user object for whom the token is being generated.
 * @return  WP_REST_Response Modified token response data.
 */
add_filter(
    "simplejwt_token_before_dispatch",
    function ($data, $user) {
        // Modify the response data.
        if ($user instanceof WP_User) {
        }
        return $data;
    },
    10,
    2,
);
</code></pre>
<h3>Credits</h3>
<ul>
<li><a href="https://developer.wordpress.org/rest-api/" rel="nofollow ugc">WordPress REST API</a></li>
<li><a href="https://github.com/firebase/php-jwt" rel="nofollow ugc">php-jwt by Firebase</a></li>
</ul>


Simple JWT Auth

Extends the WP REST API using JSON Web Tokens for robust authentication, providing a secure and reliable way to access and manage WordPress data.

WP Login and Register using JWT vs Simple JWT Auth