Stable tag: 1.3.2
Requires at least: 6.0
Tested up to: 6.0
Requires PHP: 8.0
License: GPL v2 or later
Tags: alleyinteractive, rest-api-guard
Contributors: sean212
Restrict and control access to the REST API.
You can install the package via composer:
composer require alleyinteractive/wp-rest-api-guardThe WordPress REST API is generally very public and can share a good deal of information with the internet anonymously. This plugin aims to make it easier to restrict access to the REST API for your WordPress site.
Out of the box the plugin can:
- Disable anonymous access to the REST API.
- Restrict and control anonymous access to the REST API by namespace, path, etc.
The plugin can be configured via the Settings page (Settings -> REST API Guard) or via the relevant filter.
By default, the plugin will restrict anonymous access to the users endpoint. This can be prevented in the plugin's settings or via code:
add_filter( 'rest_api_guard_allow_user_access', fn () => true );To prevent anonymous users from browsing your site and discovering what plugins/post types are set up, the plugin restricts access to the index (/) and namespace (wp/v2) endpoints. This can be prevented in the plugin's settings or via code:
// Allow index access.
add_filter( 'rest_api_guard_allow_index_access', fn () => true );
// Allow namespace access.
add_filter( 'rest_api_guard_allow_namespace_access', fn ( string $namespace ) => true );The plugin can restrict anonymous access for any request to the REST API in the plugin's settings or via code:
add_filter( 'rest_api_guard_prevent_anonymous_access', fn () => true );Anonymous users can be granted access only to specific namespaces/routes. Requests outside of these paths will be denied. This can be configured in the plugin's settings or via code:
add_filter(
'rest_api_guard_anonymous_requests_allowlist',
function ( array $paths, WP_REST_Request $request ): array {
// Allow other paths not included here will be denied.
$paths[] = 'wp/v2/post';
$paths[] = 'custom-namespace/v1/public/*';
return $paths;
},
10,
2
);Anonymous users can be restricted from specific namespaces/routes. This acts as a denylist for specific paths that an anonymous user cannot access. The paths support regular expressions for matching. The use of the Allowlist takes priority over this denylist. This can be configured in the plugin's settings or via code:
add_filter(
'rest_api_guard_anonymous_requests_denylist',
function ( array $paths, WP_REST_Request $request ): array {
$paths[] = 'wp/v2/user';
$paths[] = 'custom-namespace/v1/private/*';
return $paths;
},
10,
2
);Anonymous users can be required to authenticate via a JSON Web Token (JWT) to
access the REST API. Users should pass an Authorization: Bearer <token> header
with their request. This can be configured in the plugin's settings or via code:
add_filter( 'rest_api_guard_authentication_jwt', fn () => true );Out of the box, the plugin will look for a JWT in the Authorization: Bearer <token> header. The JWT will be expected to have an audience of
'wordpress-rest-api' and issuer of the site's URL. This can be configured in the
plugin's settings or via code:
add_filter( 'rest_api_guard_jwt_audience', fn ( string $audience ) => 'custom-audience' );
add_filter( 'rest_api_guard_jwt_issuer', fn ( string $issuer ) => 'https://example.com' );The JWT's secret will be autogenerated and stored in the
rest_api_guard_jwt_secret option. The secret can also be filtered via code:
add_filter( 'rest_api_guard_jwt_secret', fn ( string $secret ) => 'my-custom-secret' );Authenticated users can be authenticated with the REST API via a JSON Web Token.
Similar to the anonymous JWT authentication, users should pass an
Authorization: Bearer <token> header with their request. This can be
configured in the plugin's settings or via code:
add_filter( 'rest_api_guard_user_authentication_jwt', fn () => true );JWTs can be generated by calling the wp rest-api-guard generate-jwt [--user=<user_id>]
command or using the Alley\WP\REST_API_Guard\generate_jwt() method:
$jwt = \Alley\WP\REST_API_Guard\generate_jwt(
expiration: 3600, // Optional. The expiration time in seconds from now.
user: 1, // Optional. The user ID to generate the JWT for. Supports `WP_User` or user ID.
);Run composer test to run tests against PHPUnit and the PHP code in the plugin.
Please see CHANGELOG for more information on what has changed recently.
This project is actively maintained by Alley Interactive. Like what you see? Come work with us.
The GNU General Public License (GPL) license. Please see License File for more information.