000038091 - RESTful Web Service AFX Connector fails when sending a DELETE request in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Oct 29, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000038091
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 6.9.1, 7.0.x, 7.1.0, 7.1.x


 
IssueThe RESTful Web Service AFX Connector fails when sending a DELETE request in RSA Identity Governance & Lifecycle. Testing the same DELETE command using curl from the server is successful. 

The following error is seen in the user interface:



Error code = 2 
Failure - Error processing RESTful web service response
Cause:
Error processing RESTful web service response: org.xml.sax.SAXParseException: Content is not allowed




AFX REST Connector does not send body of DELETE request.



Cause

RSA Identity Governance & Lifecycle uses MuleSoft for the AFX implementation which is a third party integration software application for connecting applications, data, and devices. The reason this failure occurs is that the MuleSoft code that AFX uses to issue HTTP/HTTPS requests only sends the request body for POST and PUT requests. The request body for DELETE requests is not sent.

MuleSoft versions 3.3.2 and v3.5.2 do not allow HTTP/HTTPS DELETE body requests. This issue is logged as MuleSoft ticket MULE-8328.

ResolutionThere is no resolution at this time. This will be fixed in a future release but as of the writing of the RSA Knowledge Base Article, it is not known which release.

MuleSoft has issued a fix for this problem in the following MuleSoft versions:
  • 3.5.4 (EE Only)
  • 3.6.3 (EE Only)
  • 3.7.1 (EE Only)
  • 3.8.0
However, RSA Identity Governance & Lifecycle does not yet integrate with any of these MuleSoft versions. RSA Identity Governance & Lifecycle  6.9.1 uses MuleSoft 3.3.2 and RSA Identity Governance & Lifecycle 7.0.x, 7.1.0, and 7.1.1 use MuleSoft 3.5.2.
 
WorkaroundThe possible workarounds are:
  • If you have control over the endpoint:
    • Switch the command method used to PUT, or
    • Keep the command method as DELETE but receive the data as request parameters and/or headers rather than the request body.
  • Develop a custom JavaCodeBased Web Service Connector.

Attachments

    Outcomes