Error on Aggregation from SOAP API Call with XML Response

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hello,

I’ve setup a SOAP API call to do an aggregation for an application that I have working in Postman. In ISC I seem to be getting an HTTP Error Code 500 Unknown Error.

sailpoint.connector.ConnectorException: Url: , Message: 500 : Unknown Error, HTTP Error Code: 500

For headers I have my SOAPAction copied over from Postman and both Accept and Content-Type set as text/xml.

And my response path looks something like this:
//Node1/Node2/Node3/return/user

Where the basic XML Structure looks like this:

<Node1>
	<Node2>
		<Node3>
			<return>
				<user>
					<firstName>Test1</firstName>
					<lastName>Testing1</lastName>
				</user>
				<user>
					<firstName>Test1</firstName>
					<lastName>Testing1</lastName>
				</user>
			</return>
		</Node3>
	</Node2>
</Node1>

I thought I would check and see if anyone has any suggestions for what might be wrong with this API call?

Thanks!

2

Hi @kjerauld,

Web Services aggregation fails with an error 500

The connection to the source is timing out. This may be caused by an incorrect Base URL within the source’s configuration in SailPoint. You may see the following messages as well:

java.lang.RuntimeException - com.sailpoint.pipeline.PipelineException: An internal error occurred handling stream response from the server.

  • java.lang.RuntimeException: com.sailpoint.pipeline.PipelineException: An internal error occurred handling stream response from the server.

Caused by: java.lang.InterruptedException: Timeout waiting for response to message 63 from client

Resolution – Ensure that the Base URL is correct.

  1. In SailPoint, go to Admin > Connections > Sources.
  2. Select the appropriate Web Services source.
  3. Go to Edit Configuration > Connection Settings.
  4. Ensure the Base URL within the Server Host section is correct.If not, provide the correct URL.
  5. Save any changes you make.

Kind Regards,
Sai Krishna L

3

Error 500 could be a lot of things.
Verify the headers and the body that you send and the format of response.

4

We’ve confirmed the base URL is correct since the test connection is working and uses the same URL as our aggregation command (it’s just a POST call via SOAP API for the aggregation).

5

The headers we are using here are the same as in our Postman calls:

We have the correct SOAPAction and both Accept and Content-Type are text/xml. Interestingly enough, when we try with application/json we don’t get an error, but we also don’t get any accounts back, likely because the response is formatted in XML from the SOAP API call (it needs text/xml to work on the Postman side).

We’ve also tried formatting the response in an XPath tester with our output from Postman to make sure it is being called correctly.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.