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

MuleSoft error
403 - Forbidden, invalid client application credentials

02Likely 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

  1. Check which client application the token was issued to.
  2. Confirm that client application has access to this API instance in API Manager.
  3. Request a token for the right client application and repeat the request.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.