MuleSoft · HTTP Connector
HTTP:SECURITY
Short answer
HTTP:SECURITY means the authentication of the HTTP requester failed. Check the authentication settings and credentials on the HTTP Request configuration.
VerifiedLast verified
01Error text
Error type: HTTP:SECURITY02Likely causes
- The requester authentication failed.
03How to fix it
- Check the authentication configured on the HTTP Request configuration and the credential values for this environment.
- Turn on HTTP wire logging to see the exact request and response: in
log4j2.xml, enable the loggerorg.mule.service.http.impl.service.HttpMessageLoggeratDEBUGlevel. Confirm the authentication header is sent. - Handle the failure with an error handler of type
HTTP:SECURITY.
04Official documentation
→Related errors
- HTTP:UNAUTHORIZEDHTTP:UNAUTHORIZED means the server rejected the HTTP Request operation because authentication failed or was not provided (HTTP 401). Send the credentials the server expects, and handle the error type if a rejected call is something the flow should survive.
- HTTP:CLIENT_SECURITYHTTP:CLIENT_SECURITY means a security problem enforced by an external entity occurred during an HTTP request. Look at the more specific error, such as HTTP:UNAUTHORIZED, and fix the credentials or permissions the external system rejected.
- No access token foundNo access token found means an HTTP request with OAuth 2.0 authentication ran before any access token had been obtained. Call the authorization URL at least once first, or store the token and refresh it.
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