Gaurav Sharma

<p>Extends the WP REST API using JSON Web Tokens as an authentication method.<br />
GS JWT plugin provides to encode and decode JSON Web Tokens (JWT), conforming to RFC 7519.</p>
<p>GET OTP and send notification by mail or SMS service</p>
<p><strong>Support and Requests please in Github:</strong> https://github.com/gauravin213/gs-jwt</p>
<h3>REQUIREMENTS</h3>
<h3>PHP</h3>
<p><strong>Minimum PHP version: 5.3.0</strong></p>
<h3>PHP HTTP Authorization Header enable</h3>
<p>Most of the shared hosting has 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 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 <strong>.htaccess</strong> file adding the following</p>
<pre><code>SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
</code></pre>
<h4>CONFIGURATION</h4>
<p>The JWT needs to Add constant in the wp-confige.php file</p>
<pre><code>define( 'GS_WP_JWT_SECRET_KEY', 'your-top-secret-key' );
define( 'GS_WP_JWT_ALGO', 'HS256' );
define( 'GS_WP_JWT_EXPIRY', (60 * 60) ); //seconds * minuts
define( 'GS_WP_OTP_EXPIRY', 10);  //minuts
</code></pre>
<h3>Namespace and Endpoints</h3>
<p>When the plugin is activated, a new namespace is added</p>
<pre><code>/gs-jwt/v1
</code></pre>
<p>Also, two new endpoints are added to this namespace</p>
<p>Endpoint | HTTP Verb</p>
<p><em>/wp-json/gs-jwt/v1/login</em> | POST</p>
<p><em>/wp-json/gs-jwt/v1/token/validate</em> | POST</p>
<p><em>/wp-json/gs-jwt/v1/get-otp</em> | POST</p>
<p><em>/wp-json/gs-jwt/v1/verify-otp</em> | POST</p>
<p><em>/wp-json/gs-jwt/v1/register_user</em> | POST</p>
<p><em>/wp-json/gs-jwt/v1/register_userbymobile</em> | POST</p>
<h3>USAGE</h3>
<ol>
<li>Get JSON web token</li>
</ol>
<h4>Request method:</h4>
<pre><code>POST /wp-json/gs-jwt/v1/login

Body{
    "username": "enter username",
    "password": "enter password"
}
</code></pre>
<h4>Reponse</h4>
<pre><code>{
    "data": {
        "id": "1",
        "user_login": "admin",
        "user_pass": null,
        "user_nicename": "admin",
        "user_email": "example@gmail.com",
        "user_url": "",
        "user_registered": "2020-08-11 07:35:37",
        "user_activation_key": "",
        "user_status": "0",
        "display_name": "admin",
        "roles": [
            "administrator"
        ],
        "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC8xMjcuMC4wLjFcL3dvcmRwcmVzcyIsImlhdCI6MTY0MTk3MDIwNSwibmJmIjoxNjQxOTcwMjA1LCJleHAiOjE2NDE5NzM4MDUsImRhdGEiOnsidXNlciI6eyJpZCI6IjEifX19.gRF_aNsmhQ8kqXYdKbm6dIA7zTlhcCU-e_cpP9pQDyM"
    }
}
</code></pre>
<ol>
<li>Validate JSON web token</li>
</ol>
<h4>Request method:</h4>
<pre><code>POST /wp-json/gs-jwt/v1/token/validate

Make a POST request sending the Authorization header
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC8xMjcuMC4wLjFcL3dvcmRwcmVzcyIsImlhdCI6MTY0MTk3MDIwNSwibmJmIjoxNjQxOTcwMjA1LCJleHAiOjE2NDE5NzM4MDUsImRhdGEiOnsidXNlciI6eyJpZCI6IjEifX19.gRF_aNsmhQ8kqXYdKbm6dIA7zTlhcCU-e_cpP9pQDyM
</code></pre>
<h4>Reponse</h4>
<pre><code>{
    "code": "jwt_auth_valid_token",
    "data": {
        "status": 200
    }
}
</code></pre>
<ol>
<li>Get otp by billing mobile number</li>
</ol>
<h4>Request method:</h4>
<pre><code>POST /wp-json/gs-jwt/v1/get-otp

Body{
    "mobile": "enter mobile number"
}
</code></pre>
<h4>Reponse</h4>
<pre><code>{
    "data": {
        "otp": 249225,
        "message": "SUCCESS",
        "otp_use_staus": "0",
        "notification": {
            "mail_send_status": 0,
            "sms_send_status": 0
        }
    }
}
</code></pre>
<ol>
<li>Verify otp and mobile number to login </li>
</ol>
<h4>Request method:</h4>
<pre><code>POST /wp-json/gs-jwt/v1/verify-otp

Body{
    "otp": "enter otp",
    "mobile": "enter mobile number"
}
</code></pre>
<h4>Reponse</h4>
<pre><code>{
    "data": {
        "id": "1",
        "user_login": "admin",
        "user_pass": null,
        "user_nicename": "admin",
        "user_email": "example@gmail.com",
        "user_url": "",
        "user_registered": "2020-08-11 07:35:37",
        "user_activation_key": "",
        "user_status": "0",
        "display_name": "admin",
        "roles": [
            "administrator"
        ],
        "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC8xMjcuMC4wLjFcL3dvcmRwcmVzcyIsImlhdCI6MTY0MTk3MDIwNSwibmJmIjoxNjQxOTcwMjA1LCJleHAiOjE2NDE5NzM4MDUsImRhdGEiOnsidXNlciI6eyJpZCI6IjEifX19.gRF_aNsmhQ8kqXYdKbm6dIA7zTlhcCU-e_cpP9pQDyM"
    }
}
</code></pre>
<ol>
<li>Register user</li>
</ol>
<h4>Request method:</h4>
<pre><code>POST /wp-json/gs-jwt/v1/register_user

Body{
    "username": "example",
    "password": "example@123",
    "email": "example@gmail.com",
    "mobile": "1122336699"
}
</code></pre>
<h4>Reponse</h4>
<pre><code>{
    "data": {
        "id": 29,
        "user_login": "example",
        "user_pass": null,
        "user_nicename": "example",
        "user_email": "example@gmail.com",
        "user_url": "",
        "user_registered": "2022-01-12 07:45:29",
        "user_activation_key": "",
        "user_status": "0",
        "display_name": "example",
        "roles": [
            "customer"
        ],
        "billing_phone": "1122336699"
    },
    "code": 200,
    "message": "Registration was Successful"
}
</code></pre>
<ol>
<li>Register user by mobile number</li>
</ol>
<h4>Request method:</h4>
<pre><code>POST /wp-json/gs-jwt/v1/register_userbymobile

Body{
    "mobile": "1122336699"
}
</code></pre>
<h4>Reponse</h4>
<pre><code>{
    "data": {
        "id": 32,
        "user_login": "1144556638",
        "user_nicename": "1144556638",
        "user_registered": "2022-01-13 06:29:30",
        "display_name": "1144556638",
        "roles": [
            "customer"
        ],
        "billing_phone": "1144556638"
    },
    "code": 200,
    "message": "Registration was Successful"
}
</code></pre>
<h4>Sample add SMS and email notification</h4>
<pre><code>/*
* Send notification 
* Default mail_send_status = 0, sms_send_status = 0
*/
function gs_wp_jwt_send_notification_fun( $data, $user_id, $otp, $mobile ) {

  //Write mail send code here
  $from = get_option('admin_email');
  $to = get_user_meta($user_id, 'billing_email', true);
  $subject = "OTP Verification";
  $message = "OTP number: {$opt} will expire in 10 min";
  $headers = "From: ".$from;
  $result = wp_mail( $to, $subject, $message, $headers);

  if ($result) { 

    $data['mail_send_status'] = 1;

  } //end mail send


  //Write sms send api code here
  /*if ($sms_send_status) { 

    $data['sms_send_status'] = 1;

  } //ens sms send*/

  return $data;
}
add_filter( 'gs_wp_jwt_send_notification', 'gs_wp_jwt_send_notification_fun', 10, 4 );
</code></pre>


GS JWT Authentication for WP REST API

Extends the WP REST API using JSON Web Tokens as an authentication method.

tmeister

<p>This plugin seamlessly extends the WP REST API, enabling robust and secure authentication using JSON Web Tokens (JWT). It provides a straightforward way to authenticate users via the REST API, returning a standard JWT upon successful login.</p>
<h3>Key features of this free version include:</h3>
<ul>
<li><strong>Standard JWT Authentication:</strong> Implements the industry-standard <a href="https://tools.ietf.org/html/rfc7519" rel="nofollow ugc">RFC 7519</a> for secure claims representation.</li>
<li><strong>Simple Endpoints:</strong> Offers clear <code>/token</code> and <code>/token/validate</code> endpoints for generating and validating tokens.</li>
<li><strong>Configurable Secret Key:</strong> Define your unique secret key via <code>wp-config.php</code> for secure token signing.</li>
<li><strong>Optional CORS Support:</strong> Easily enable Cross-Origin Resource Sharing support via a <code>wp-config.php</code> constant.</li>
<li><strong>Developer Hooks:</strong> Provides filters (<code>jwt_auth_expire</code>, <code>jwt_auth_token_before_sign</code>, etc.) for customizing token behavior.</li>
</ul>
<p>JSON Web Tokens are an open, industry standard method for representing claims securely between two parties.</p>
<p>For users requiring more advanced capabilities such as multiple signing algorithms (RS256, ES256), token refresh/revocation, UI-based configuration, or priority support, consider checking out <strong><a href="https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=description_link_soft" rel="nofollow ugc">JWT Authentication PRO</a></strong>.</p>
<p><strong>Support and Requests:</strong> Please use <a href="https://github.com/Tmeister/wp-api-jwt-auth/issues" rel="nofollow ugc">GitHub Issues</a>. For priority support, consider upgrading to <a href="https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=description_support_link" rel="nofollow ugc">PRO</a>.</p>
<h3>REQUIREMENTS</h3>
<h4>WP REST API V2</h4>
<p>This plugin was conceived to extend the <a href="https://github.com/WP-API/WP-API" rel="nofollow ugc">WP REST API V2</a> plugin features and, of course, was built on top of it.</p>
<p>So, to use the <strong>wp-api-jwt-auth</strong> you need to install and activate <a href="https://github.com/WP-API/WP-API" rel="nofollow ugc">WP REST API</a>.</p>
<h3>PHP</h3>
<p><strong>Minimum PHP version: 7.4.0</strong></p>
<h3>PHP HTTP Authorization Header Enable</h3>
<p>Most shared hosting providers 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>For WPEngine hosting, you’ll need to edit your <strong>.htaccess</strong> file by adding the following:</p>
<pre><code>SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
</code></pre>
<p>See https://github.com/Tmeister/wp-api-jwt-auth/issues/1 for more details.</p>
<h3>CONFIGURATION</h3>
<h3>Configure the Secret Key</h3>
<p>The JWT needs a <strong>secret key</strong> to sign the token. This <strong>secret key</strong> must be unique and never revealed.</p>
<p>To add the <strong>secret key</strong>, edit your wp-config.php file and add a new constant called <strong>JWT_AUTH_SECRET_KEY</strong>:</p>
<pre><code>define('JWT_AUTH_SECRET_KEY', 'your-top-secret-key');
</code></pre>
<p>You can generate a secure key from: https://api.wordpress.org/secret-key/1.1/salt/</p>
<p><strong>Looking for easier configuration?</strong> <a href="https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=config_secret_key_link" rel="nofollow ugc">JWT Authentication PRO</a> allows you to manage all settings through a simple admin UI.</p>
<h3>Configure CORS Support</h3>
<p>The <strong>wp-api-jwt-auth</strong> plugin has the option to activate <a href="https://en.wikipedia.org/wiki/Cross-origin_resource_sharing" rel="nofollow ugc">CORS</a> support.</p>
<p>To enable CORS Support, edit your wp-config.php file and add a new constant called <strong>JWT_AUTH_CORS_ENABLE</strong>:</p>
<pre><code>define('JWT_AUTH_CORS_ENABLE', true);
</code></pre>
<p>Finally, activate the plugin within your wp-admin.</p>
<h3>Namespace and Endpoints</h3>
<p>When the plugin is activated, a new namespace is added:</p>
<pre><code>/jwt-auth/v1
</code></pre>
<p>Also, two new endpoints are added to this namespace:</p>
<p>Endpoint | HTTP Verb<br />
<em>/wp-json/jwt-auth/v1/token</em> | POST<br />
<em>/wp-json/jwt-auth/v1/token/validate</em> | POST</p>
<p><strong>Need more functionality?</strong> <a href="https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=endpoints_pro_note" rel="nofollow ugc">JWT Authentication PRO</a> includes additional endpoints for token refresh and revocation.</p>
<h3>USAGE</h3>
<h4>/wp-json/jwt-auth/v1/token</h4>
<p>This is the entry point for JWT Authentication.</p>
<p>It validates the user credentials, <em>username</em> and <em>password</em>, and returns a token to use in future requests to the API if the authentication is correct, or an error if authentication fails.</p>
<p>Sample Request Using AngularJS</p>
<pre><code>(function() {
  var app = angular.module('jwtAuth', []);

  app.controller('MainController', function($scope, $http) {
    var apiHost = 'http://yourdomain.com/wp-json';

    $http.post(apiHost + '/jwt-auth/v1/token', {
      username: 'admin',
      password: 'password'
    })
    .then(function(response) {
      console.log(response.data)
    })
    .catch(function(error) {
      console.error('Error', error.data[0]);
    });
  });
})();
</code></pre>
<p>Success Response From The Server</p>
<pre><code>{
  "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC9qd3QuZGV2IiwiaWF0IjoxNDM4NTcxMDUwLCJuYmYiOjE0Mzg1NzEwNTAsImV4cCI6MTQzOTE3NTg1MCwiZGF0YSI6eyJ1c2VyIjp7ImlkIjoiMSJ9fX0.YNe6AyWW4B7ZwfFE5wJ0O6qQ8QFcYizimDmBy6hCH_8",
  "user_display_name": "admin",
  "user_email": "admin@localhost.dev",
  "user_nicename": "admin"
}
</code></pre>
<p>Error Response From The Server</p>
<pre><code>{
  "code": "jwt_auth_failed",
  "data": {
    "status": 403
  },
  "message": "Invalid Credentials."
}
</code></pre>
<p>Once you get the token, you must store it somewhere in your application, e.g., in a <strong>cookie</strong> or using <strong>localStorage</strong>.</p>
<p>From this point, you should pass this token with every API call.</p>
<p>Sample Call Using The Authorization Header With AngularJS</p>
<pre><code>app.config(function($httpProvider) {
  $httpProvider.interceptors.push(['$q', '$location', '$cookies', function($q, $location, $cookies) {
    return {
      'request': function(config) {
        config.headers = config.headers || {};
        // Assume that you store the token in a cookie
        var globals = $cookies.getObject('globals') || {};
        // If the cookie has the CurrentUser and the token
        // add the Authorization header in each request
        if (globals.currentUser && globals.currentUser.token) {
          config.headers.Authorization = 'Bearer ' + globals.currentUser.token;
        }
        return config;
      }
    };
  }]);
});
</code></pre>
<p>The <strong>wp-api-jwt-auth</strong> plugin will intercept every call to the server and will look for the Authorization Header. If the Authorization header is present, it will try to decode the token and will set the user according to the data stored in it.</p>
<p>If the token is valid, the API call flow will continue as normal.</p>
<p><strong>Sample Headers</strong></p>
<pre><code>POST /resource HTTP/1.1
Host: server.example.com
Authorization: Bearer mF_s9.B5f-4.1JqM
</code></pre>
<h3>ERRORS</h3>
<p>If the token is invalid, an error will be returned. Here are some sample errors:</p>
<p><strong>Invalid Credentials</strong></p>
<pre><code>[
  {
    "code": "jwt_auth_failed",
    "message": "Invalid Credentials.",
    "data": {
      "status": 403
    }
  }
]
</code></pre>
<p><strong>Invalid Signature</strong></p>
<pre><code>[
  {
    "code": "jwt_auth_invalid_token",
    "message": "Signature verification failed",
    "data": {
      "status": 403
    }
  }
]
</code></pre>
<p><strong>Expired Token</strong></p>
<pre><code>[
  {
    "code": "jwt_auth_invalid_token",
    "message": "Expired token",
    "data": {
      "status": 403
    }
  }
]
</code></pre>
<p><strong>Need advanced error tracking?</strong> <a href="https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=errors_pro_note" rel="nofollow ugc">JWT Authentication PRO</a> offers enhanced error tracking and monitoring capabilities.</p>
<h4>/wp-json/jwt-auth/v1/token/validate</h4>
<p>This is a simple helper endpoint to validate a token. You only need to make a POST request with the Authorization header.</p>
<p><strong>Valid Token Response</strong></p>
<pre><code>{
  "code": "jwt_auth_valid_token",
  "data": {
    "status": 200
  }
}
</code></pre>
<h3>AVAILABLE HOOKS</h3>
<p>The <strong>wp-api-jwt-auth</strong> plugin is developer-friendly and provides five filters to override the default settings.</p>
<h4>jwt_auth_cors_allow_headers</h4>
<p>The <strong>jwt_auth_cors_allow_headers</strong> filter allows you to modify the available headers when CORS support is enabled.</p>
<p>Default Value:</p>
<pre><code>'Access-Control-Allow-Headers, Content-Type, Authorization'
</code></pre>
<h4>jwt_auth_not_before</h4>
<p>The <strong>jwt_auth_not_before</strong> filter 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 token is created.</p>
<p>Default Value:</p>
<pre><code>Creation time - time()
</code></pre>
<h4>jwt_auth_expire</h4>
<p>The <strong>jwt_auth_expire</strong> filter allows you to change the <a href="https://tools.ietf.org/html/rfc7519#section-4.1.4" rel="nofollow ugc"><strong>exp</strong></a> value before the token is created.</p>
<p>Default Value:</p>
<pre><code>time() + (DAY_IN_SECONDS * 7)
</code></pre>
<h4>jwt_auth_token_before_sign</h4>
<p>The <strong>jwt_auth_token_before_sign</strong> filter allows you to modify all token data before it is encoded and signed.</p>
<p>Default Value:</p>
<pre><code>$token = array(
    'iss' => get_bloginfo('url'),
    'iat' => $issuedAt,
    'nbf' => $notBefore,
    'exp' => $expire,
    'data' => array(
        'user' => array(
            'id' => $user->data->ID,
        )
    )
);
</code></pre>
<p><strong>Want easier customization?</strong> <a href="https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=hook_payload_pro_note" rel="nofollow ugc">JWT Authentication PRO</a> allows you to add custom claims directly through the admin UI.</p>
<h4>jwt_auth_token_before_dispatch</h4>
<p>The <strong>jwt_auth_token_before_dispatch</strong> filter allows you to modify the response array before it is sent to the client.</p>
<p>Default Value:</p>
<pre><code>$data = array(
    'token' => $token,
    'user_email' => $user->data->user_email,
    'user_nicename' => $user->data->user_nicename,
    'user_display_name' => $user->data->display_name,
);
</code></pre>
<h4>jwt_auth_algorithm</h4>
<p>The <strong>jwt_auth_algorithm</strong> filter allows you to modify the signing algorithm.</p>
<p>Default value:</p>
<pre><code>$token = JWT::encode(
    apply_filters('jwt_auth_token_before_sign', $token, $user),
    $secret_key,
    apply_filters('jwt_auth_algorithm', 'HS256')
);

// ...

$token = JWT::decode(
    $token,
    new Key($secret_key, apply_filters('jwt_auth_algorithm', 'HS256'))
);
</code></pre>
<h3>JWT Authentication PRO</h3>
<p>Elevate your WordPress security and integration capabilities with <strong>JWT Authentication PRO</strong>. Building upon the solid foundation of the free version, the PRO version offers advanced features, enhanced security options, and a streamlined user experience:</p>
<ul>
<li><strong>Easy Configuration UI:</strong> Manage all settings directly from the WordPress admin area.</li>
<li><strong>Token Refresh Endpoint:</strong> Allow users to refresh expired tokens seamlessly without requiring re-login.</li>
<li><strong>Token Revocation Endpoint:</strong> Immediately invalidate specific tokens for enhanced security control.</li>
<li><strong>Customizable Token Payload:</strong> Add custom claims to your JWT payload to suit your specific application needs.</li>
<li><strong>Granular CORS Control:</strong> Define allowed origins and headers with more precision directly in the settings.</li>
<li><strong>Rate Limiting:</strong> Protect your endpoints from abuse with configurable rate limits.</li>
<li><strong>Audit Logs:</strong> Keep track of token generation, validation, and errors.</li>
<li><strong>Priority Support:</strong> Get faster, dedicated support directly from the developer.</li>
</ul>
<p><strong><a href="https://jwtauth.pro/?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=pro_section_cta" rel="nofollow ugc">Upgrade to JWT Authentication PRO Today!</a></strong></p>
<h3>Free vs. PRO Comparison</h3>
<p>Here’s a quick look at the key differences:</p>
<ul>
<li><strong>Basic JWT Authentication:</strong> Included (Free), Included (PRO)</li>
<li><strong>Token Generation:</strong> Included (Free), Included (PRO)</li>
<li><strong>Token Validation:</strong> Included (Free), Included (PRO)</li>
<li><strong>Token Refresh Mechanism:</strong> Not Included (Free), Included (PRO)</li>
<li><strong>Token Revocation:</strong> Not Included (Free), Included (PRO)</li>
<li><strong>Token Management Dashboard:</strong> Not Included (Free), Included (PRO)</li>
<li><strong>Analytics & Monitoring:</strong> Not Included (Free), Included (PRO)</li>
<li><strong>Geo-IP Identification:</strong> Not Included (Free), Included (PRO)</li>
<li><strong>Rate Limiting:</strong> Not Included (Free), Included (PRO)</li>
<li><strong>Detailed Documentation:</strong> Basic (Free), Comprehensive (PRO)</li>
<li><strong>Developer Tools:</strong> Not Included (Free), Included (PRO)</li>
<li><strong>Premium Support:</strong> Community via GitHub (Free), Priority Direct Support (PRO)</li>
</ul>


JWT Authentication for WP REST API

I was confused about choosing the jwt plugin. There are 3 versions, the first has not been updated for 6 months and the second has not been updated for two months, the first has not worked, the second has unclear instructions and has some defects despite the presence of a dashboard, and this add-on has not been updated for two years  But when I saw that it was updated a day ago, I decided to use it and all the problems that I was facing were resolved. I ask the add-on developers to update them every period, but there is something unclear, how can I amend the token expiry time?  Thanks

good


It breaks APIs that don't require authorization.



Such as WordPress's posts endpoint and WooCommerce's endpoint.


It breaks APIs that don't require authorization


Perfect! This plugin is very easy to install and use. It's also easy to extend and add your own return data.


Easy to use and extend


I've been using the plugin for over year, it's very good and user friendly!



At some point there was a constant message to upgrade, but that was fixed.


Great plugin!

Extends the WP REST API using JSON Web Tokens Authentication as an authentication method.

GS JWT Authentication for WP REST API vs JWT Authentication for WP REST API