Hi everyone,
We’re currently implementing a Web Service integration via MuleSoft from SailPoint Identity Security Cloud (ISC) to perform update operations on a target system.
Here’s the setup and what we’re facing:
-
Integration flow: SailPoint ISC → MuleSoft API → Target web service
-
Payload format: SOAP XML (MuleSoft converts SOAP → REST → Target)
-
Authentication: Azure AD OAuth 2.0 (client credentials)
-
Connector type: Web Service Connector
-
Rule used: Before Operation Rule (to build SOAP body and set headers)
Current Issue:
-
We are getting the following exception when performing the Modify operation:
Exception occurred while performing 'Modify' operation on identity '1056': Error executing before operation rule for endpoint 'Add Entitlement-RoleId': bsh.EvalError: Method put(java.lang.String, java.lang.String) not found in class 'sailpoint.connector.webservices.EndPoint' -
The SOAP request payload and OAuth token are generated successfully, but the update call to MuleSoft fails with HTTP 406 (
SCHEMA_VALIDATION/APIKIT_ERROR). -
The MuleSoft team confirmed that the API accepts both JSON and SOAP payloads and automatically transforms between them.
Questions:
-
For SOAP integrations via MuleSoft, what’s the recommended configuration for the Web Service connector source in ISC (Content-Type, SOAPAction, etc.)?
-
In a Before Operation Rule, should we use
requestEndPoint.setBody()andsetHeader()for SOAP, or should we return a Map as in a Before Sending Rule? -
Has anyone successfully configured a SOAP → MuleSoft → REST flow for update operations? Any working examples or best practices would be great.
What we’ve tried:
-
Switched between
application/soap+xmlandtext/xml -
Adjusted SOAP Action header
-
Removed SOAP envelope (also tested with envelope)
Any guidance, working examples, or configuration recommendations would be appreciated!
Thanks in advance,
Venky