MuleSoft · OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider policy
403 Forbidden, invalid client application credentials
Short answer
An API protected by the OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider policy returns 403 when the client application credentials behind the token are invalid for this API. Use a token issued to a client application that has access to the API.
VerifiedLast verified
01Error text
403 - Forbidden, invalid client application credentials02Likely causes
- The client application credentials are invalid.
- Client ID validation is on (Skip Client Id Validation is off), so the token's client must be valid for this API.
03How to fix it
- Check which client application the token was issued to.
- Confirm that client application has access to this API instance in API Manager.
- Request a token for the right client application and repeat the request.
04Official documentation
→Related errors
- 400 Invalid tokenAn API protected by the OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider policy returns 400 when the access token is invalid. Request a new token from the provider and send that one.
- 401 Unauthorized or invalid client application credentialsAn API protected by the Client ID Enforcement policy returns 401 when the client application's credentials are missing, invalid or not authorized. The client needs an approved contract for the API and must send matching credentials on every request.
- HTTP:FORBIDDENHTTP:FORBIDDEN means the server refused to return the resource because the client does not have access rights to it (HTTP 403). The credentials were sent, so fix the permissions of the identity behind them on the target system.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer