API Bearer Auth vs Orbisius Limit Logins

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

This plugin logs and blocks IP address of users who try to login with known bad usernames such as admin, adm etc. The plugin intentionally hooks very early (plugins_loaded hook) in order to determine if the user should be blocked or not because that way WordPress doesn’t have to waste resources if the user is supposed to be blocked. It stores the IP address in the uploads folder (.htaccess protected) so it doesn’t hit the database for the ip checks. This may not work on some setups. The user will get blocked in these cases: – Tries to login using one of the bad usernames (admin, adm, root, administrator) – Tries 7 or more ties to guess any password of any user Note: If you still have an account whose username matches the logins mentioned above please create a new admin account and use that one instead .. or you will get banned when you attempt to login regardless if your password was valid or not. When the user should be blocked the plugin outputs Internal Server Error message and stop. That way the attacked doesn’t know what’s happening. Also the user is has to wait between 3 and 15 seconds before seeing this error message to slow him/her down. Features / Benefits Hooks very early and checks if the user is blocked -> blocks to saves resources Doesn’t block server’s ip or localhost / 127.0.0.1 The plugin should be capable of detecting multiple IP address of a visitor (some proxies pass the original IP address via different request variable) If an IP is blocked that user is not allowed to access the whole site not just the login page. Extensible via hooks (filters, actions). Demo TODO Bugs? Suggestions? If you want a faster response contact us through our website’s contact form [ orbisius.com ] and not through the support tab of this plugin or WordPress forums. We don’t get notified when such requests get posted in the forums. Support is handled on our site: http://club.orbisius.com/forums/ Please do NOT use the WordPress forums or other places to seek support. Author Svetoslav Marinov (Slavi) | Custom Web and Mobile Programming by Orbisius.com