MuleSoft · JWT Validation policy

400 Token was not provided in the request

Short answer

An API protected by the JWT Validation policy returns 400 when the request carries no token where the policy looks for it. Send the JWT in the place the policy's JWT Origin and Token Expression settings name.

VerifiedLast verified

01Error text

MuleSoft error
400 - Token was not provided in the request.

02Likely causes

  • The token was not provided in the request.
  • The token is sent somewhere other than where the policy's JWT Origin or Token Expression reads it.

03How to fix it

  1. Open the policy configuration in API Manager and check JWT Origin and, if it is used, Token Expression.
  2. Send the JWT in that location on every request.
  3. 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.