[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f6973huziRAzVpfk4S4fBOHxTvuKg919OwLuewZfGRrY":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":39,"analysis":139,"fingerprints":227},"jwt-authentication-for-wp-rest-api","JWT Authentication for WP REST API","1.5.0","tmeister","https:\u002F\u002Fprofiles.wordpress.org\u002Ftmeister\u002F","\u003Cp>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.\u003C\u002Fp>\n\u003Ch3>Key features of this free version include:\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Standard JWT Authentication:\u003C\u002Fstrong> Implements the industry-standard \u003Ca href=\"https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7519\" rel=\"nofollow ugc\">RFC 7519\u003C\u002Fa> for secure claims representation.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Simple Endpoints:\u003C\u002Fstrong> Offers clear \u003Ccode>\u002Ftoken\u003C\u002Fcode> and \u003Ccode>\u002Ftoken\u002Fvalidate\u003C\u002Fcode> endpoints for generating and validating tokens.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Configurable Secret Key:\u003C\u002Fstrong> Define your unique secret key via \u003Ccode>wp-config.php\u003C\u002Fcode> for secure token signing.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Optional CORS Support:\u003C\u002Fstrong> Easily enable Cross-Origin Resource Sharing support via a \u003Ccode>wp-config.php\u003C\u002Fcode> constant.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Developer Hooks:\u003C\u002Fstrong> Provides filters (\u003Ccode>jwt_auth_expire\u003C\u002Fcode>, \u003Ccode>jwt_auth_token_before_sign\u003C\u002Fcode>, etc.) for customizing token behavior.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>JSON Web Tokens are an open, industry standard method for representing claims securely between two parties.\u003C\u002Fp>\n\u003Cp>For users requiring more advanced capabilities such as multiple signing algorithms (RS256, ES256), token refresh\u002Frevocation, UI-based configuration, or priority support, consider checking out \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=description_link_soft\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Support and Requests:\u003C\u002Fstrong> Please use \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FTmeister\u002Fwp-api-jwt-auth\u002Fissues\" rel=\"nofollow ugc\">GitHub Issues\u003C\u002Fa>. For priority support, consider upgrading to \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=description_support_link\" rel=\"nofollow ugc\">PRO\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>REQUIREMENTS\u003C\u002Fh3>\n\u003Ch4>WP REST API V2\u003C\u002Fh4>\n\u003Cp>This plugin was conceived to extend the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWP-API\u002FWP-API\" rel=\"nofollow ugc\">WP REST API V2\u003C\u002Fa> plugin features and, of course, was built on top of it.\u003C\u002Fp>\n\u003Cp>So, to use the \u003Cstrong>wp-api-jwt-auth\u003C\u002Fstrong> you need to install and activate \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWP-API\u002FWP-API\" rel=\"nofollow ugc\">WP REST API\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>PHP\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Minimum PHP version: 7.4.0\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>PHP HTTP Authorization Header Enable\u003C\u002Fh3>\n\u003Cp>Most shared hosting providers have disabled the \u003Cstrong>HTTP Authorization Header\u003C\u002Fstrong> by default.\u003C\u002Fp>\n\u003Cp>To enable this option you’ll need to edit your \u003Cstrong>.htaccess\u003C\u002Fstrong> file by adding the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>RewriteEngine on\nRewriteCond %{HTTP:Authorization} ^(.*)\nRewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>WPENGINE\u003C\u002Fh4>\n\u003Cp>For WPEngine hosting, you’ll need to edit your \u003Cstrong>.htaccess\u003C\u002Fstrong> file by adding the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>SetEnvIf Authorization \"(.*)\" HTTP_AUTHORIZATION=$1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>See https:\u002F\u002Fgithub.com\u002FTmeister\u002Fwp-api-jwt-auth\u002Fissues\u002F1 for more details.\u003C\u002Fp>\n\u003Ch3>CONFIGURATION\u003C\u002Fh3>\n\u003Ch3>Configure the Secret Key\u003C\u002Fh3>\n\u003Cp>The JWT needs a \u003Cstrong>secret key\u003C\u002Fstrong> to sign the token. This \u003Cstrong>secret key\u003C\u002Fstrong> must be unique and never revealed.\u003C\u002Fp>\n\u003Cp>To add the \u003Cstrong>secret key\u003C\u002Fstrong>, edit your wp-config.php file and add a new constant called \u003Cstrong>JWT_AUTH_SECRET_KEY\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('JWT_AUTH_SECRET_KEY', 'your-top-secret-key');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can generate a secure key from: https:\u002F\u002Fapi.wordpress.org\u002Fsecret-key\u002F1.1\u002Fsalt\u002F\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Looking for easier configuration?\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=config_secret_key_link\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa> allows you to manage all settings through a simple admin UI.\u003C\u002Fp>\n\u003Ch3>Configure CORS Support\u003C\u002Fh3>\n\u003Cp>The \u003Cstrong>wp-api-jwt-auth\u003C\u002Fstrong> plugin has the option to activate \u003Ca href=\"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCross-origin_resource_sharing\" rel=\"nofollow ugc\">CORS\u003C\u002Fa> support.\u003C\u002Fp>\n\u003Cp>To enable CORS Support, edit your wp-config.php file and add a new constant called \u003Cstrong>JWT_AUTH_CORS_ENABLE\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('JWT_AUTH_CORS_ENABLE', true);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Finally, activate the plugin within your wp-admin.\u003C\u002Fp>\n\u003Ch3>Namespace and Endpoints\u003C\u002Fh3>\n\u003Cp>When the plugin is activated, a new namespace is added:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002Fjwt-auth\u002Fv1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Also, two new endpoints are added to this namespace:\u003C\u002Fp>\n\u003Cp>Endpoint | HTTP Verb\u003Cbr \u002F>\n\u003Cem>\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u003C\u002Fem> | POST\u003Cbr \u002F>\n\u003Cem>\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u002Fvalidate\u003C\u002Fem> | POST\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Need more functionality?\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=endpoints_pro_note\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa> includes additional endpoints for token refresh and revocation.\u003C\u002Fp>\n\u003Ch3>USAGE\u003C\u002Fh3>\n\u003Ch4>\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u003C\u002Fh4>\n\u003Cp>This is the entry point for JWT Authentication.\u003C\u002Fp>\n\u003Cp>It validates the user credentials, \u003Cem>username\u003C\u002Fem> and \u003Cem>password\u003C\u002Fem>, and returns a token to use in future requests to the API if the authentication is correct, or an error if authentication fails.\u003C\u002Fp>\n\u003Cp>Sample Request Using AngularJS\u003C\u002Fp>\n\u003Cpre>\u003Ccode>(function() {\n  var app = angular.module('jwtAuth', []);\n\n  app.controller('MainController', function($scope, $http) {\n    var apiHost = 'http:\u002F\u002Fyourdomain.com\u002Fwp-json';\n\n    $http.post(apiHost + '\u002Fjwt-auth\u002Fv1\u002Ftoken', {\n      username: 'admin',\n      password: 'password'\n    })\n    .then(function(response) {\n      console.log(response.data)\n    })\n    .catch(function(error) {\n      console.error('Error', error.data[0]);\n    });\n  });\n})();\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Success Response From The Server\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"token\": \"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC9qd3QuZGV2IiwiaWF0IjoxNDM4NTcxMDUwLCJuYmYiOjE0Mzg1NzEwNTAsImV4cCI6MTQzOTE3NTg1MCwiZGF0YSI6eyJ1c2VyIjp7ImlkIjoiMSJ9fX0.YNe6AyWW4B7ZwfFE5wJ0O6qQ8QFcYizimDmBy6hCH_8\",\n  \"user_display_name\": \"admin\",\n  \"user_email\": \"admin@localhost.dev\",\n  \"user_nicename\": \"admin\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Error Response From The Server\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"code\": \"jwt_auth_failed\",\n  \"data\": {\n    \"status\": 403\n  },\n  \"message\": \"Invalid Credentials.\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Once you get the token, you must store it somewhere in your application, e.g., in a \u003Cstrong>cookie\u003C\u002Fstrong> or using \u003Cstrong>localStorage\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>From this point, you should pass this token with every API call.\u003C\u002Fp>\n\u003Cp>Sample Call Using The Authorization Header With AngularJS\u003C\u002Fp>\n\u003Cpre>\u003Ccode>app.config(function($httpProvider) {\n  $httpProvider.interceptors.push(['$q', '$location', '$cookies', function($q, $location, $cookies) {\n    return {\n      'request': function(config) {\n        config.headers = config.headers || {};\n        \u002F\u002F Assume that you store the token in a cookie\n        var globals = $cookies.getObject('globals') || {};\n        \u002F\u002F If the cookie has the CurrentUser and the token\n        \u002F\u002F add the Authorization header in each request\n        if (globals.currentUser && globals.currentUser.token) {\n          config.headers.Authorization = 'Bearer ' + globals.currentUser.token;\n        }\n        return config;\n      }\n    };\n  }]);\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The \u003Cstrong>wp-api-jwt-auth\u003C\u002Fstrong> 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.\u003C\u002Fp>\n\u003Cp>If the token is valid, the API call flow will continue as normal.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Sample Headers\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>POST \u002Fresource HTTP\u002F1.1\nHost: server.example.com\nAuthorization: Bearer mF_s9.B5f-4.1JqM\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>ERRORS\u003C\u002Fh3>\n\u003Cp>If the token is invalid, an error will be returned. Here are some sample errors:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Invalid Credentials\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[\n  {\n    \"code\": \"jwt_auth_failed\",\n    \"message\": \"Invalid Credentials.\",\n    \"data\": {\n      \"status\": 403\n    }\n  }\n]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Invalid Signature\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[\n  {\n    \"code\": \"jwt_auth_invalid_token\",\n    \"message\": \"Signature verification failed\",\n    \"data\": {\n      \"status\": 403\n    }\n  }\n]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Expired Token\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[\n  {\n    \"code\": \"jwt_auth_invalid_token\",\n    \"message\": \"Expired token\",\n    \"data\": {\n      \"status\": 403\n    }\n  }\n]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Need advanced error tracking?\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=errors_pro_note\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa> offers enhanced error tracking and monitoring capabilities.\u003C\u002Fp>\n\u003Ch4>\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u002Fvalidate\u003C\u002Fh4>\n\u003Cp>This is a simple helper endpoint to validate a token. You only need to make a POST request with the Authorization header.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Valid Token Response\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"code\": \"jwt_auth_valid_token\",\n  \"data\": {\n    \"status\": 200\n  }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>AVAILABLE HOOKS\u003C\u002Fh3>\n\u003Cp>The \u003Cstrong>wp-api-jwt-auth\u003C\u002Fstrong> plugin is developer-friendly and provides five filters to override the default settings.\u003C\u002Fp>\n\u003Ch4>jwt_auth_cors_allow_headers\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_cors_allow_headers\u003C\u002Fstrong> filter allows you to modify the available headers when CORS support is enabled.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'Access-Control-Allow-Headers, Content-Type, Authorization'\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>jwt_auth_not_before\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_not_before\u003C\u002Fstrong> filter allows you to change the \u003Ca href=\"https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7519#section-4.1.5\" rel=\"nofollow ugc\">\u003Cstrong>nbf\u003C\u002Fstrong>\u003C\u002Fa> value before the token is created.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Creation time - time()\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>jwt_auth_expire\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_expire\u003C\u002Fstrong> filter allows you to change the \u003Ca href=\"https:\u002F\u002Ftools.ietf.org\u002Fhtml\u002Frfc7519#section-4.1.4\" rel=\"nofollow ugc\">\u003Cstrong>exp\u003C\u002Fstrong>\u003C\u002Fa> value before the token is created.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>time() + (DAY_IN_SECONDS * 7)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>jwt_auth_token_before_sign\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_token_before_sign\u003C\u002Fstrong> filter allows you to modify all token data before it is encoded and signed.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$token = array(\n    'iss' => get_bloginfo('url'),\n    'iat' => $issuedAt,\n    'nbf' => $notBefore,\n    'exp' => $expire,\n    'data' => array(\n        'user' => array(\n            'id' => $user->data->ID,\n        )\n    )\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Want easier customization?\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?utm_source=wp_plugin_readme&utm_medium=link&utm_campaign=pro_promotion&utm_content=hook_payload_pro_note\" rel=\"nofollow ugc\">JWT Authentication PRO\u003C\u002Fa> allows you to add custom claims directly through the admin UI.\u003C\u002Fp>\n\u003Ch4>jwt_auth_token_before_dispatch\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_token_before_dispatch\u003C\u002Fstrong> filter allows you to modify the response array before it is sent to the client.\u003C\u002Fp>\n\u003Cp>Default Value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$data = array(\n    'token' => $token,\n    'user_email' => $user->data->user_email,\n    'user_nicename' => $user->data->user_nicename,\n    'user_display_name' => $user->data->display_name,\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>jwt_auth_algorithm\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>jwt_auth_algorithm\u003C\u002Fstrong> filter allows you to modify the signing algorithm.\u003C\u002Fp>\n\u003Cp>Default value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$token = JWT::encode(\n    apply_filters('jwt_auth_token_before_sign', $token, $user),\n    $secret_key,\n    apply_filters('jwt_auth_algorithm', 'HS256')\n);\n\n\u002F\u002F ...\n\n$token = JWT::decode(\n    $token,\n    new Key($secret_key, apply_filters('jwt_auth_algorithm', 'HS256'))\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>JWT Authentication PRO\u003C\u002Fh3>\n\u003Cp>Elevate your WordPress security and integration capabilities with \u003Cstrong>JWT Authentication PRO\u003C\u002Fstrong>. Building upon the solid foundation of the free version, the PRO version offers advanced features, enhanced security options, and a streamlined user experience:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Easy Configuration UI:\u003C\u002Fstrong> Manage all settings directly from the WordPress admin area.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Refresh Endpoint:\u003C\u002Fstrong> Allow users to refresh expired tokens seamlessly without requiring re-login.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Revocation Endpoint:\u003C\u002Fstrong> Immediately invalidate specific tokens for enhanced security control.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Customizable Token Payload:\u003C\u002Fstrong> Add custom claims to your JWT payload to suit your specific application needs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Granular CORS Control:\u003C\u002Fstrong> Define allowed origins and headers with more precision directly in the settings.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rate Limiting:\u003C\u002Fstrong> Protect your endpoints from abuse with configurable rate limits.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit Logs:\u003C\u002Fstrong> Keep track of token generation, validation, and errors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Priority Support:\u003C\u002Fstrong> Get faster, dedicated support directly from the developer.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fjwtauth.pro\u002F?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!\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Free vs. PRO Comparison\u003C\u002Fh3>\n\u003Cp>Here’s a quick look at the key differences:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Basic JWT Authentication:\u003C\u002Fstrong> Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Generation:\u003C\u002Fstrong> Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Validation:\u003C\u002Fstrong> Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Refresh Mechanism:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Revocation:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Token Management Dashboard:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Analytics & Monitoring:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Geo-IP Identification:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rate Limiting:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Detailed Documentation:\u003C\u002Fstrong> Basic (Free), Comprehensive (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Developer Tools:\u003C\u002Fstrong> Not Included (Free), Included (PRO)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Premium Support:\u003C\u002Fstrong> Community via GitHub (Free), Priority Direct Support (PRO)\u003C\u002Fli>\n\u003C\u002Ful>\n","Extends the WP REST API using JSON Web Tokens Authentication as an authentication method.",60000,893830,88,53,"2026-02-18T00:58:00.000Z","6.9.4","4.2","7.4.0",[20,21,22,23,24],"json-web-authentication","jwt","oauth","rest-api","wp-api","https:\u002F\u002Fenriquechavez.co","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjwt-authentication-for-wp-rest-api.1.5.0.zip",100,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":35,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},2,63000,93,30,89,"2026-04-03T23:33:40.155Z",[40,59,75,98,120],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":48,"downloaded":49,"rating":27,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":53,"tags":54,"homepage":56,"download_link":57,"security_score":58,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"custom-fields-for-jwt-authentication-for-wp-rest-api","User Data Fields For JWT Authentication","1.2.1","Ahmed Hnewa","https:\u002F\u002Fprofiles.wordpress.org\u002Fahmedriyadh\u002F","\u003Cp>WordPress is a good content mangement system for building websites, but it will be better if you build like mobile apps,\u003Cbr \u002F>\nWith the wordpress rest api you can create posts, edit posts, view posts, Users, Uploading Media etc…\u003Cbr \u002F>\nbut the problem with the wordpress rest api it does not provide any authentication methods for third party application like mobile apps\u003Cbr \u002F>\nThe Jwt Plugin on wordpress.org does provide that\u003C\u002Fp>\n\u003Cp>and this plugin is just a addon for that plugin\u003C\u002Fp>\n\u003Cp>So this plugin is useful if you don’t want to make another request to fetch user data like Id etc..\u003Cbr \u002F>\nbecause you have to get the id of the user in ordet to get all data\u003C\u002Fp>\n\u003Cp>It really simple plugin\u003Cbr \u002F>\nit writed with 50 lines of code, the size of the plugin is 3Kb\u003C\u002Fp>\n\u003Cp>Note: This Is Plugin For\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjwt-authentication-for-wp-rest-api\u002F\" rel=\"ugc\">JWT Authentication for WP REST API Plugin\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>so if the jwt authentication plugin is not installed\u003Cbr \u002F>\nthis plugin will not add the fields to it endpoints\u003C\u002Fp>\n\u003Cp>and the fields will be added only if the token is getted successfully\u003C\u002Fp>\n\u003Cp>Example request (before install the plugin):\u003Cbr \u002F>\n{\u003Cbr \u002F>\n    “token”: “eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC8xOTIuMTY4LjAuMTgyIiwiaWF0IjoxNjE0MDg3NDQ2LCJuYmYiOjE2MTQwODc0NDYsImV4cCI6MTYxNDY5MjI0NiwiZGF0YSI6eyJ1c2VyIjp7ImlkIjoiMSJ9fX0.KeAUc7PiTne0_PThsSAWo1ruvl2Ocu-fbCn2jG7zkoE”,\u003Cbr \u002F>\n    “user_email”: “example@example.com”,\u003Cbr \u002F>\n    “user_nicename”: “admin”,\u003Cbr \u002F>\n    “user_display_name”: “admin”\u003Cbr \u002F>\n}\u003C\u002Fp>\n\u003Cp>Example response (after install the plugin):\u003Cbr \u002F>\n{\u003Cbr \u002F>\n    “token”: “eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC8xOTIuMTY4LjAuMTgyIiwiaWF0IjoxNjE0MDg2NjQyLCJuYmYiOjE2MTQwODY2NDIsImV4cCI6MTYxNDY5MTQ0MiwiZGF0YSI6eyJ1c2VyIjp7ImlkIjoiMSJ9fX0.nyDOICdQcZKbWZo2kQRp_eLBkuxjnK_rpxs-HJREyCg”,\u003Cbr \u002F>\n    “user_email”: “example@example.com”,\u003Cbr \u002F>\n    “user_nicename”: “admin”,\u003Cbr \u002F>\n    “user_display_name”: “admin”,\u003Cbr \u002F>\n    “user_id”: 1,\u003Cbr \u002F>\n    “user_login”: “admin”,\u003Cbr \u002F>\n    “user_first_name”: “sfd”,\u003Cbr \u002F>\n    “user_last_name”: “”,\u003Cbr \u002F>\n    “user_roles”: [\u003Cbr \u002F>\n        “administrator”\u003Cbr \u002F>\n    ],\u003Cbr \u002F>\n    “user_role”: “administrator”,\u003Cbr \u002F>\n    “user_registered”: “2021-02-17 09:21:29”,\u003Cbr \u002F>\n    “user_url”: “http:\u002F\u002Flocalhost”,\u003Cbr \u002F>\n    “user_status”: “0”,\u003Cbr \u002F>\n    “user_avatar_url”: “https:\u002F\u002Fsecure.gravatar.com\u002Favatar\u002F22feea4605ac5b7163eac439b5241034?s=96&d=mm&r=g”,\u003Cbr \u002F>\n    “user_activation_key”: “”\u003Cbr \u002F>\n}\u003C\u002Fp>\n\u003Cp>Of course you can add the code of this plugin to your Theme,\u003Cbr \u002F>\nbut this is not recommened because when you change the theme or update it\u003Cbr \u002F>\nthe changes will revert back, you can create child theme for that\u003Cbr \u002F>\nbut instead you can just install this simple plugin\u003C\u002Fp>\n\u003Cp>Don’t forget to setup (JwtAuthenticatonForWordpress)[https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjwt-authentication-for-wp-rest-api\u002F]\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fahmedhnewa\u002Fuser-data-fields-jwt-plugin\" rel=\"nofollow ugc\">Github\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Can Add User Data Fields To Validate Token Endpoint ?\u003C\u002Fh3>\n\u003Cp>This plugin can also add user data fields to validate token endpoint,\u003C\u002Fp>\n\u003Cp>Unfortunately, the jwt extension does not support using the filter for validate_token function,\u003Cbr \u002F>\nSo You Will Need To Modify Some Codes Inside Jwt Plugin Codes\u003Cbr \u002F>\nGo To \\wp-content\\plugins\\jwt-authentication-for-wp-rest-api\\public\\class-jwt-auth-public.php\u003Cbr \u002F>\nAnd At The End Of Function That Named validate_token\u003Cbr \u002F>\nIn Line 302\u003C\u002Fp>\n\u003Cp>Edit This Code\u003Cbr \u002F>\nFrom :\u003Cbr \u002F>\n\u002F** If the output is true return an answer to the request to show it *\u002F\u003Cbr \u002F>\n            return array(\u003Cbr \u002F>\n                ‘code’ => ‘jwt_auth_valid_token’,\u003Cbr \u002F>\n                ‘data’ => array(\u003Cbr \u002F>\n                    ‘status’ => 200,\u003Cbr \u002F>\n                ),\u003Cbr \u002F>\n            );\u003Cbr \u002F>\nTo :\u003Cbr \u002F>\n$value = array(\u003Cbr \u002F>\n            ‘code’ => ‘jwt_auth_valid_token’,\u003Cbr \u002F>\n                ‘data’ => array(\u003Cbr \u002F>\n                    ‘status’ => 200,\u003Cbr \u002F>\n                )\u003Cbr \u002F>\n            );\u003Cbr \u002F>\n            \u002F** If the output is true return an answer to the request to show it *\u002F\u003Cbr \u002F>\n            return apply_filters(‘jwt_auth_validate_token’, $value, $token);\u003C\u002Fp>\n\u003Cp>Now you have done,\u003Cbr \u002F>\nthe plugin should be able to add new values by adding a filter\u003C\u002Fp>\n\u003Cp>Note :\u003Cbr \u002F>\nIf you updated the jwt plugin,\u003Cbr \u002F>\nyou should again edit the code because it will be removed\u003C\u002Fp>\n\u003Ch3>REQUIREMENTS\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjwt-authentication-for-wp-rest-api\u002F\" rel=\"ugc\">JWT Authentication for WP REST API Plugin\u003C\u002Fa>\u003C\u002Fp>\n","Wordpress is a good content mangement system for building websites, but it will be better if you build like mobile apps,",40,2337,3,"2022-08-01T18:33:00.000Z","6.0.11","",[20,21,24,55],"wp-json","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcustom-fields-for-jwt-authentication-for-wp-rest-api\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-fields-for-jwt-authentication-for-wp-rest-api.1.2.1.zip",85,{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":28,"num_ratings":28,"last_updated":69,"tested_up_to":70,"requires_at_least":17,"requires_php":71,"tags":72,"homepage":53,"download_link":74,"security_score":58,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"gs-jwt-auth-and-otp-varification","GS JWT Authentication for WP REST API","1.0.0","Gaurav Sharma","https:\u002F\u002Fprofiles.wordpress.org\u002Fgauravin213\u002F","\u003Cp>Extends the WP REST API using JSON Web Tokens as an authentication method.\u003Cbr \u002F>\nGS JWT plugin provides to encode and decode JSON Web Tokens (JWT), conforming to RFC 7519.\u003C\u002Fp>\n\u003Cp>GET OTP and send notification by mail or SMS service\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Support and Requests please in Github:\u003C\u002Fstrong> https:\u002F\u002Fgithub.com\u002Fgauravin213\u002Fgs-jwt\u003C\u002Fp>\n\u003Ch3>REQUIREMENTS\u003C\u002Fh3>\n\u003Ch3>PHP\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Minimum PHP version: 5.3.0\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>PHP HTTP Authorization Header enable\u003C\u002Fh3>\n\u003Cp>Most of the shared hosting has disabled the \u003Cstrong>HTTP Authorization Header\u003C\u002Fstrong> by default.\u003C\u002Fp>\n\u003Cp>To enable this option you’ll need to edit your \u003Cstrong>.htaccess\u003C\u002Fstrong> file adding the following\u003C\u002Fp>\n\u003Cpre>\u003Ccode>RewriteEngine on\nRewriteCond %{HTTP:Authorization} ^(.*)\nRewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>WPENGINE\u003C\u002Fh4>\n\u003Cp>To enable this option you’ll need to edit your \u003Cstrong>.htaccess\u003C\u002Fstrong> file adding the following\u003C\u002Fp>\n\u003Cpre>\u003Ccode>SetEnvIf Authorization \"(.*)\" HTTP_AUTHORIZATION=$1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>CONFIGURATION\u003C\u002Fh4>\n\u003Cp>The JWT needs to Add constant in the wp-confige.php file\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'GS_WP_JWT_SECRET_KEY', 'your-top-secret-key' );\ndefine( 'GS_WP_JWT_ALGO', 'HS256' );\ndefine( 'GS_WP_JWT_EXPIRY', (60 * 60) ); \u002F\u002Fseconds * minuts\ndefine( 'GS_WP_OTP_EXPIRY', 10);  \u002F\u002Fminuts\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Namespace and Endpoints\u003C\u002Fh3>\n\u003Cp>When the plugin is activated, a new namespace is added\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002Fgs-jwt\u002Fv1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Also, two new endpoints are added to this namespace\u003C\u002Fp>\n\u003Cp>Endpoint | HTTP Verb\u003C\u002Fp>\n\u003Cp>\u003Cem>\u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Flogin\u003C\u002Fem> | POST\u003C\u002Fp>\n\u003Cp>\u003Cem>\u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Ftoken\u002Fvalidate\u003C\u002Fem> | POST\u003C\u002Fp>\n\u003Cp>\u003Cem>\u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Fget-otp\u003C\u002Fem> | POST\u003C\u002Fp>\n\u003Cp>\u003Cem>\u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Fverify-otp\u003C\u002Fem> | POST\u003C\u002Fp>\n\u003Cp>\u003Cem>\u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Fregister_user\u003C\u002Fem> | POST\u003C\u002Fp>\n\u003Cp>\u003Cem>\u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Fregister_userbymobile\u003C\u002Fem> | POST\u003C\u002Fp>\n\u003Ch3>USAGE\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Get JSON web token\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Request method:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>POST \u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Flogin\n\nBody{\n    \"username\": \"enter username\",\n    \"password\": \"enter password\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Reponse\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>{\n    \"data\": {\n        \"id\": \"1\",\n        \"user_login\": \"admin\",\n        \"user_pass\": null,\n        \"user_nicename\": \"admin\",\n        \"user_email\": \"example@gmail.com\",\n        \"user_url\": \"\",\n        \"user_registered\": \"2020-08-11 07:35:37\",\n        \"user_activation_key\": \"\",\n        \"user_status\": \"0\",\n        \"display_name\": \"admin\",\n        \"roles\": [\n            \"administrator\"\n        ],\n        \"token\": \"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC8xMjcuMC4wLjFcL3dvcmRwcmVzcyIsImlhdCI6MTY0MTk3MDIwNSwibmJmIjoxNjQxOTcwMjA1LCJleHAiOjE2NDE5NzM4MDUsImRhdGEiOnsidXNlciI6eyJpZCI6IjEifX19.gRF_aNsmhQ8kqXYdKbm6dIA7zTlhcCU-e_cpP9pQDyM\"\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Col>\n\u003Cli>Validate JSON web token\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Request method:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>POST \u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Ftoken\u002Fvalidate\n\nMake a POST request sending the Authorization header\nAuthorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC8xMjcuMC4wLjFcL3dvcmRwcmVzcyIsImlhdCI6MTY0MTk3MDIwNSwibmJmIjoxNjQxOTcwMjA1LCJleHAiOjE2NDE5NzM4MDUsImRhdGEiOnsidXNlciI6eyJpZCI6IjEifX19.gRF_aNsmhQ8kqXYdKbm6dIA7zTlhcCU-e_cpP9pQDyM\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Reponse\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>{\n    \"code\": \"jwt_auth_valid_token\",\n    \"data\": {\n        \"status\": 200\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Col>\n\u003Cli>Get otp by billing mobile number\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Request method:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>POST \u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Fget-otp\n\nBody{\n    \"mobile\": \"enter mobile number\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Reponse\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>{\n    \"data\": {\n        \"otp\": 249225,\n        \"message\": \"SUCCESS\",\n        \"otp_use_staus\": \"0\",\n        \"notification\": {\n            \"mail_send_status\": 0,\n            \"sms_send_status\": 0\n        }\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Col>\n\u003Cli>Verify otp and mobile number to login \u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Request method:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>POST \u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Fverify-otp\n\nBody{\n    \"otp\": \"enter otp\",\n    \"mobile\": \"enter mobile number\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Reponse\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>{\n    \"data\": {\n        \"id\": \"1\",\n        \"user_login\": \"admin\",\n        \"user_pass\": null,\n        \"user_nicename\": \"admin\",\n        \"user_email\": \"example@gmail.com\",\n        \"user_url\": \"\",\n        \"user_registered\": \"2020-08-11 07:35:37\",\n        \"user_activation_key\": \"\",\n        \"user_status\": \"0\",\n        \"display_name\": \"admin\",\n        \"roles\": [\n            \"administrator\"\n        ],\n        \"token\": \"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwOlwvXC8xMjcuMC4wLjFcL3dvcmRwcmVzcyIsImlhdCI6MTY0MTk3MDIwNSwibmJmIjoxNjQxOTcwMjA1LCJleHAiOjE2NDE5NzM4MDUsImRhdGEiOnsidXNlciI6eyJpZCI6IjEifX19.gRF_aNsmhQ8kqXYdKbm6dIA7zTlhcCU-e_cpP9pQDyM\"\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Col>\n\u003Cli>Register user\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Request method:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>POST \u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Fregister_user\n\nBody{\n    \"username\": \"example\",\n    \"password\": \"example@123\",\n    \"email\": \"example@gmail.com\",\n    \"mobile\": \"1122336699\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Reponse\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>{\n    \"data\": {\n        \"id\": 29,\n        \"user_login\": \"example\",\n        \"user_pass\": null,\n        \"user_nicename\": \"example\",\n        \"user_email\": \"example@gmail.com\",\n        \"user_url\": \"\",\n        \"user_registered\": \"2022-01-12 07:45:29\",\n        \"user_activation_key\": \"\",\n        \"user_status\": \"0\",\n        \"display_name\": \"example\",\n        \"roles\": [\n            \"customer\"\n        ],\n        \"billing_phone\": \"1122336699\"\n    },\n    \"code\": 200,\n    \"message\": \"Registration was Successful\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Col>\n\u003Cli>Register user by mobile number\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Request method:\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>POST \u002Fwp-json\u002Fgs-jwt\u002Fv1\u002Fregister_userbymobile\n\nBody{\n    \"mobile\": \"1122336699\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Reponse\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>{\n    \"data\": {\n        \"id\": 32,\n        \"user_login\": \"1144556638\",\n        \"user_nicename\": \"1144556638\",\n        \"user_registered\": \"2022-01-13 06:29:30\",\n        \"display_name\": \"1144556638\",\n        \"roles\": [\n            \"customer\"\n        ],\n        \"billing_phone\": \"1144556638\"\n    },\n    \"code\": 200,\n    \"message\": \"Registration was Successful\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Sample add SMS and email notification\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>\u002F*\n* Send notification \n* Default mail_send_status = 0, sms_send_status = 0\n*\u002F\nfunction gs_wp_jwt_send_notification_fun( $data, $user_id, $otp, $mobile ) {\n\n  \u002F\u002FWrite mail send code here\n  $from = get_option('admin_email');\n  $to = get_user_meta($user_id, 'billing_email', true);\n  $subject = \"OTP Verification\";\n  $message = \"OTP number: {$opt} will expire in 10 min\";\n  $headers = \"From: \".$from;\n  $result = wp_mail( $to, $subject, $message, $headers);\n\n  if ($result) { \n\n    $data['mail_send_status'] = 1;\n\n  } \u002F\u002Fend mail send\n\n\n  \u002F\u002FWrite sms send api code here\n  \u002F*if ($sms_send_status) { \n\n    $data['sms_send_status'] = 1;\n\n  } \u002F\u002Fens sms send*\u002F\n\n  return $data;\n}\nadd_filter( 'gs_wp_jwt_send_notification', 'gs_wp_jwt_send_notification_fun', 10, 4 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Extends the WP REST API using JSON Web Tokens as an authentication method.",10,1032,"2022-01-13T07:09:00.000Z","5.8.13","5.3.0",[20,21,73,24,55],"otp","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgs-jwt-auth-and-otp-varification.1.0.0.zip",{"slug":76,"name":77,"version":78,"author":79,"author_profile":80,"description":81,"short_description":82,"active_installs":83,"downloaded":84,"rating":13,"num_ratings":85,"last_updated":86,"tested_up_to":16,"requires_at_least":87,"requires_php":88,"tags":89,"homepage":94,"download_link":95,"security_score":96,"vuln_count":33,"unpatched_count":28,"last_vuln_date":97,"fetched_at":30},"wp-rest-api-authentication","JWT Authentication for WP REST APIs","4.3.0","miniOrange","https:\u002F\u002Fprofiles.wordpress.org\u002Fcyberlord92\u002F","\u003Cp>\u003Cstrong>WordPress REST API endpoints\u003C\u002Fstrong> are \u003Cstrong>open and unsecured by default\u003C\u002Fstrong> which can be used to access your site data. Secure WordPress APIs from unauthorized users with our \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Fwordpress-rest-api-authentication\" rel=\"nofollow ugc\">JWT Authentication for WP REST APIs plugin\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>Our plugin offers below authentication methods to \u003Cstrong>Protect WP REST API endpoints\u003C\u002Fstrong>:\u003Cbr \u002F>\n– \u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Fwordpress-rest-api-jwt-authentication-method\" rel=\"nofollow ugc\">JWT Authentication\u003C\u002Fa>\u003Cbr \u002F>\n– \u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Fwordpress-rest-api-basic-authentication-method\" rel=\"nofollow ugc\">Basic Authentication\u003C\u002Fa>\u003Cbr \u002F>\n– \u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Frest-api-key-authentication-method\" rel=\"nofollow ugc\">API Key Authentication\u003C\u002Fa>\u003Cbr \u002F>\n– \u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Fwordpress-rest-api-oauth-2-0-authentication-method\" rel=\"nofollow ugc\">OAuth 2.0 Authentication\u003C\u002Fa>\u003Cbr \u002F>\n– External Token based Authentication 2.0\u002FOIDC\u002FJWT\u002F\u003Ca href=\"https:\u002F\u002Ffirebase.google.com\u002Fdocs\u002Fauth\u002Fadmin\u002Fcreate-custom-tokens\" rel=\"nofollow ugc\">Firebase\u003C\u002Fa> provider’s token authentication methods.\u003C\u002Fp>\n\u003Cp>You can authenticate default WordPress endpoints and custom-developed REST endpoints and third-party plugin REST API endpoints like that of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwoocommerce\u002F\" rel=\"ugc\">Woocommerce\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.learndash.com\u002F\" rel=\"nofollow ugc\">Learndash\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fbuddypress\u002F\" rel=\"ugc\">Buddypress\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.gravityforms.com\u002F\" rel=\"nofollow ugc\">Gravity Forms\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcart-rest-api-for-woocommerce\u002F\" rel=\"ugc\">CoCart\u003C\u002Fa>, etc.\u003C\u002Fp>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FIsyKI7eEV-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\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Ch3>WP REST API Authentication Methods in our plugin\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Fwordpress-rest-api-jwt-authentication-method#step_a1\" rel=\"nofollow ugc\">JWT Authentication\u003C\u002Fa>\u003Cbr \u002F>\nProvides 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.\u003Cbr \u002F>\nAdditionally, to maintain a seamless user experience without frequent logins needed due to token expiry, you can use our \u003Cem>Refresh and Revoke token\u003C\u002Fem> mechanisms feature.\u003Cbr \u002F>\nWhen 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.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Frest-api-key-authentication-method#step_a\" rel=\"nofollow ugc\">API Key Authentication\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Fwordpress-rest-api-basic-authentication-method\" rel=\"nofollow ugc\">Basic Authentication\u003C\u002Fa>:\u003Cbr \u002F>\n        – 1. \u003Cstrong>Username: Password\u003C\u002Fstrong>\u003Cbr \u002F>\n        – 2. \u003Cstrong>Client-ID: Client-Secret\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Fwordpress-rest-api-oauth-2-0-authentication-method#step_a\" rel=\"nofollow ugc\">OAuth 2.0 Authentication\u003C\u002Fa>\u003Cbr \u002F>\n        – 1. \u003Cstrong>Password Grant\u003C\u002Fstrong>\u003Cbr \u002F>\n            – 2. \u003Cstrong>Client Credentials Grant\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugins.miniorange.com\u002Fwordpress-rest-api-authentication-using-third-party-provider#step_a\" rel=\"nofollow ugc\">Third Party Provider Authentication\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Following are some of the integrations that are possible with WP REST API Authentication:\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Learndash API Authentication\u003C\u002Fli>\n\u003Cli>Custom Built REST API Endpoints Authentication\u003C\u002Fli>\n\u003Cli>BuddyPress API Authentication\u003C\u002Fli>\n\u003Cli>WooCommerce API Authentication\u003C\u002Fli>\n\u003Cli>Gravity Form API Authentication\u003C\u002Fli>\n\u003Cli>External\u002FThird-party plugin API endpoints integration in WordPress\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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 \u003Cstrong>Refresh and Revoke Token\u003C\u002Fstrong> that can be used to improve the API security.\u003C\u002Fp>\n\u003Ch3>Benefits of Refresh Token\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Enhances security by keeping access tokens short-lived.\u003C\u002Fli>\n\u003Cli>Improves user experience with uninterrupted sessions.\u003C\u002Fli>\n\u003Cli>Reduces login frequency.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Benefits of Revoke Token\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Protects against token misuse if a device is lost or compromised.\u003C\u002Fli>\n\u003Cli>Enables admin-triggered logouts or session control.\u003C\u002Fli>\n\u003Cli>Useful for complying with stricter session policies.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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 \u003Cstrong>WordPress endpoints secure from unauthorized access.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Plugin Feature List\u003C\u002Fh3>\n\u003Ch3>FREE PLAN\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Authenticate only default core WordPress REST API endpoints.\u003C\u002Fli>\n\u003Cli>Basic Authentication with username and password.\u003C\u002Fli>\n\u003Cli>JWT Authentication (JSON Web Token Authentication).\u003C\u002Fli>\n\u003Cli>Enable Selective API protection.\u003C\u002Fli>\n\u003Cli>Restrict non-logged-in users to access REST API endpoints.\u003C\u002Fli>\n\u003Cli>Disable WP REST APIs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>PREMIUM PLAN\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Authenticate all REST API endpoints (Default WP, Custom APIs,Third-Party plugins)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>JWT Token Authentication\u003C\u002Fstrong> (JSON Web Token Authentication)\u003C\u002Fli>\n\u003Cli>Login, Refresh and Revoke token endpoints for token management\u003C\u002Fli>\n\u003Cli>API Key Authentication\u003C\u002Fli>\n\u003Cli>Basic Authentication (username\u002Fpassword and email\u002Fpassword)\u003C\u002Fli>\n\u003Cli>OAuth 2.0 Authentication\u003C\u002Fli>\n\u003Cli>Universal API key and User-specific API key for authentication\u003C\u002Fli>\n\u003Cli>Selective API protection.\u003C\u002Fli>\n\u003Cli>Disable WP REST APIs\u003C\u002Fli>\n\u003Cli>Time-based token expiry\u003C\u002Fli>\n\u003Cli>Role-based WP REST API authentication\u003C\u002Fli>\n\u003Cli>Custom Header support rather than just \u003Cem>Authorization\u003C\u002Fem> to increase security.\u003C\u002Fli>\n\u003Cli>Create users in WordPress based on third-party provider access tokens (JWT tokens) authentication.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>This plugin does not store any user data.\u003C\u002Fp>\n","Secure and protect WordPress REST API from unauthorized access using JWT token, Basic Authentication, API Key, OAuth 2, or external token.",20000,490496,73,"2026-02-09T05:11:00.000Z","3.0.1","5.6",[90,91,92,23,93],"api-key","jwt-authentication","rest","secure-api","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-rest-api-authentication","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-rest-api-authentication.4.3.0.zip",97,"2025-04-16 00:00:00",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":108,"num_ratings":109,"last_updated":110,"tested_up_to":111,"requires_at_least":112,"requires_php":53,"tags":113,"homepage":117,"download_link":118,"security_score":119,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-rest-api-log","REST API Log","1.7.0","Pete Nelson","https:\u002F\u002Fprofiles.wordpress.org\u002Fgungeekatx\u002F","\u003Cp>WordPress plugin to log \u003Ca href=\"http:\u002F\u002Fv2.wp-api.org\u002F\" rel=\"nofollow ugc\">REST API\u003C\u002Fa> requests and responses (for v2 of the API).\u003C\u002Fp>\n\u003Cp>Includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress admin page to view and search log entries\u003C\u002Fli>\n\u003Cli>API endpoint to access log entries via JSON\u003C\u002Fli>\n\u003Cli>Filters to customize logging\u003C\u002Fli>\n\u003Cli>Custom endpoint logging\u003C\u002Fli>\n\u003Cli>ElasticPress logging\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Find us on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpetenelson\u002Fwp-rest-api-log\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>!\u003C\u002Fp>\n\u003Cp>Roadmap\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Better search capabilities for log entries via the REST API endpoint\u003C\u002Fli>\n\u003C\u002Ful>\n","WordPress plugin to log REST API requests and responses",5000,113000,72,24,"2025-01-02T16:29:00.000Z","6.7.5","4.7",[114,115,23,24,116],"api","json","wp-rest-api","https:\u002F\u002Fgithub.com\u002Fpetenelson\u002Fwp-rest-api-log","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-rest-api-log.1.7.0.zip",92,{"slug":121,"name":122,"version":123,"author":124,"author_profile":125,"description":126,"short_description":127,"active_installs":128,"downloaded":129,"rating":27,"num_ratings":130,"last_updated":131,"tested_up_to":132,"requires_at_least":133,"requires_php":53,"tags":134,"homepage":137,"download_link":138,"security_score":58,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-api-menus","WP API Menus","1.3.2","Fulvio Notarstefano","https:\u002F\u002Fprofiles.wordpress.org\u002Fnekojira\u002F","\u003Cp>This plugin extends the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjson-rest-api\u002F\" rel=\"ugc\">WordPress JSON REST API\u003C\u002Fa> with new routes for WordPress registered menus\u003C\u002Fp>\n\u003Cp>The new routes available will be:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>\u002Fmenus\u003C\u002Fcode> list of every registered menu.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fmenus\u002F\u003Cid>\u003C\u002Fcode> data for a specific menu.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fmenu-locations\u003C\u002Fcode> list of all registered theme locations.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fmenu-locations\u002F\u003Clocation>\u003C\u002Fcode> data for menu in specified menu in theme location.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Currently, the \u003Ccode>menu-locations\u002F\u003Clocation>\u003C\u002Fcode> route for individual menus will return a tree with full menu hierarchy, with correct menu item order and listing children for each menu item. The \u003Ccode>menus\u002F\u003Cid>\u003C\u002Fcode> route will output menu details and a flat array of menu items. Item order or if each item has a parent will be indicated in each item attributes, but this route won’t output items as a tree.\u003C\u002Fp>\n\u003Cp>You can alter the data arrangement of each individual menu items and children using the filter hook \u003Ccode>json_menus_format_menu_item\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>An important note on WP API V2:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>In V1 the routes are located by default at \u003Ccode>wp-json\u002Fmenus\u002F\u003C\u002Fcode> etc.\u003C\u002Fp>\n\u003Cp>In V2 the routes by default are at \u003Ccode>wp-json\u002Fwp-api-menus\u002Fv2\u002F\u003C\u002Fcode> (e.g. \u003Ccode>wp-json\u002Fwp-api-menus\u002Fv2\u002Fmenus\u002F\u003C\u002Fcode>, etc.) since V2 encourages prefixing and version namespacing.\u003C\u002Fp>\n","Extends WordPress WP REST API with new routes pointing to WordPress menus.",2000,107511,8,"2020-08-18T07:21:00.000Z","5.5.0","3.6.0",[115,135,136,24,116],"json-rest-api","menus","https:\u002F\u002Fgithub.com\u002Fnekojira\u002Fwp-api-menus","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-api-menus.1.3.2.zip",{"attackSurface":140,"codeSignals":200,"taintFlows":212,"riskAssessment":213,"analyzedAt":226},{"hooks":141,"ajaxHandlers":194,"restRoutes":195,"shortcodes":196,"cronEvents":197,"entryPointCount":28,"unprotectedCount":28},[142,148,152,156,161,164,166,169,172,175,178,181,183,185,187,190],{"type":143,"name":144,"callback":145,"file":146,"line":147},"action","admin_head","closure","admin\\class-jwt-auth-admin.php",569,{"type":149,"name":150,"callback":145,"priority":67,"file":146,"line":151},"filter","script_loader_tag",601,{"type":143,"name":153,"callback":145,"priority":154,"file":146,"line":155},"admin_footer",5,636,{"type":143,"name":157,"callback":158,"file":159,"line":160},"plugins_loaded","anonymous","includes\\class-jwt-auth.php",150,{"type":143,"name":162,"callback":158,"file":159,"line":163},"rest_api_init",161,{"type":149,"name":162,"callback":158,"file":159,"line":165},162,{"type":149,"name":167,"callback":158,"file":159,"line":168},"rest_pre_dispatch",163,{"type":149,"name":170,"callback":158,"file":159,"line":171},"determine_current_user",164,{"type":143,"name":173,"callback":158,"file":159,"line":174},"admin_menu",175,{"type":143,"name":176,"callback":158,"file":159,"line":177},"admin_enqueue_scripts",176,{"type":143,"name":179,"callback":158,"file":159,"line":180},"admin_init",177,{"type":143,"name":179,"callback":158,"file":159,"line":182},178,{"type":143,"name":162,"callback":158,"file":159,"line":184},179,{"type":143,"name":162,"callback":158,"file":159,"line":186},180,{"type":143,"name":188,"callback":158,"file":159,"line":189},"admin_notices",181,{"type":143,"name":191,"callback":191,"file":192,"line":193},"jwt_auth_share_data","jwt-auth.php",65,[],[],[],[198],{"hook":191,"callback":191,"file":192,"line":199},50,{"dangerousFunctions":201,"sqlUsage":202,"outputEscaping":205,"fileOperations":28,"externalRequests":50,"nonceChecks":28,"capabilityChecks":33,"bundledLibraries":211},[],{"prepared":203,"raw":28,"locations":204},1,[],{"escaped":206,"rawEcho":203,"locations":207},21,[208],{"file":146,"line":209,"context":210},658,"raw output",[],[],{"summary":214,"deductions":215},"The jwt-authentication-for-wp-rest-api plugin version 1.5.0 demonstrates a generally strong security posture based on the provided static analysis and vulnerability history. The absence of direct entry points like AJAX handlers and REST API routes without proper permission callbacks, along with the lack of critical code signals such as dangerous functions and raw SQL queries, are positive indicators. The plugin also shows good practices in output escaping, with 95% of outputs being properly handled, and utilizes prepared statements for its single SQL query, which mitigates the risk of SQL injection.\n\nHowever, there are a few areas that warrant attention. The presence of a cron event, while not inherently insecure, represents a potential execution point that could be exploited if not properly secured or if it interacts with other components in an unexpected way. Furthermore, the plugin performs three external HTTP requests, which could be a vector for various attacks if the target URLs are compromised or if the data sent\u002Freceived is not validated or escaped thoroughly. The lack of nonce checks on any entry points, though zero are identified, is a missed opportunity for a common WordPress security layer, and the limited capability checks (only two) suggest that authentication and authorization might be less granular than ideal.\n\nHistorically, the plugin has a clean record with zero known CVEs of any severity, indicating a consistent effort towards security. This, combined with the current analysis, suggests the developers are generally security-conscious. The strengths lie in the careful handling of direct code execution paths and data sanitization. The weaknesses, though minor in this version, lie in potential indirect execution points like cron jobs and external requests, and the limited use of WordPress's built-in security mechanisms like nonces. Overall, the plugin appears relatively secure for version 1.5.0, but ongoing vigilance is always recommended, especially concerning external dependencies and cron job functionalities.",[216,218,221,223],{"reason":217,"points":50},"Cron event present",{"reason":219,"points":220},"External HTTP requests (3)",6,{"reason":222,"points":154},"No nonce checks",{"reason":224,"points":225},"Limited capability checks (2)",4,"2026-03-16T17:15:45.482Z",{"wat":228,"direct":241},{"assetPaths":229,"generatorPatterns":234,"scriptPaths":235,"versionParams":236},[230,231,232,233],"\u002Fwp-content\u002Fplugins\u002Fjwt-authentication-for-wp-rest-api\u002Fadmin\u002Fcss\u002Fjwt-auth-admin.css","\u002Fwp-content\u002Fplugins\u002Fjwt-authentication-for-wp-rest-api\u002Fadmin\u002Fjs\u002Fjwt-auth-admin.js","\u002Fwp-content\u002Fplugins\u002Fjwt-authentication-for-wp-rest-api\u002Fpublic\u002Fcss\u002Fjwt-auth-public.css","\u002Fwp-content\u002Fplugins\u002Fjwt-authentication-for-wp-rest-api\u002Fpublic\u002Fjs\u002Fjwt-auth-public.js",[],[],[237,238,239,240],"jwt-authentication-for-wp-rest-api\u002Fadmin\u002Fcss\u002Fjwt-auth-admin.css?ver=","jwt-authentication-for-wp-rest-api\u002Fadmin\u002Fjs\u002Fjwt-auth-admin.js?ver=","jwt-authentication-for-wp-rest-api\u002Fpublic\u002Fcss\u002Fjwt-auth-public.css?ver=","jwt-authentication-for-wp-rest-api\u002Fpublic\u002Fjs\u002Fjwt-auth-public.js?ver=",{"cssClasses":242,"htmlComments":246,"htmlAttributes":247,"restEndpoints":249,"jsGlobals":262,"shortcodeOutput":267},[243,244,245],"jwt-auth-admin-settings-page","jwt-auth-settings-section","jwt-auth-notice-wrapper",[],[248],"data-jwt-auth-settings",[250,251,252,253,254,255,256,257,258,259,260,261],"\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fadmin\u002Fsettings","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fadmin\u002Fstatus","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fadmin\u002Fsurvey","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fadmin\u002Fsurvey\u002Fstatus","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fadmin\u002Fsurvey\u002Fcomplete","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fadmin\u002Fsurvey\u002Fdismissal","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fadmin\u002Fdashboard","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fusers\u002Ftokens","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fusers\u002Flogin","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Fusers\u002Flogout","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u002Fvalidate","\u002Fwp-json\u002Fjwt-auth\u002Fv1\u002Ftoken\u002Frefresh",[263,264,265,266],"jwtAuthAdmin","jwtAuthAdminSettings","jwtAuthPublic","jwtAuthToken",[]]