MuleSoft · IP Allowlist policy

403 IP is rejected

Short answer

An API protected by the IP Allowlist policy returns 403 when the caller's IP address is not in the allowlist. Add the address or range to the allowlist, or fix the IP expression if the API sits behind a proxy.

VerifiedLast verified

01Error text

MuleSoft error
403 - IP is rejected

02Likely causes

  • The IP address the policy extracted from the request is not in the Allowlist.
  • Behind a proxy or load balancer, the IP expression has to read the original client address, for example from the x-Forwarded-For header.

03How to fix it

  1. Find the IP address the caller's requests arrive from.
  2. In API Manager, add it to the policy's Allowlist as a single IP (192.168.1.1), a subnet (192.168.3.1/30) or an octet range (192.168).
  3. If the API is behind a proxy, set IP expression to a DataWeave expression that reads the client address from the forwarded header.
  4. Repeat the request.

iNotes

The docs describe configuration only. The steps above apply the documented settings to the documented 403.

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.