PARTNERS - Please join us for our upcoming webinar:
Leveraging Intelligent Recommendations for Operational Transformation.
AMS Partners click HERE | EMEA/APJ Partners click HERE

SOAP Connector: error 500, Wrong Content-Type and empty HTTP-Body received

Olesia
Regular Contributor
Regular Contributor

Hi,

I've been working on integrating a SOAP-based application with Saviynt using a SOAP connector. The connection works fine from SOAP UI and Postman but from Saviynt we are getting an Internal Server Error (500) "SRT: Wrong Content-Type and empty HTTP-Body received".

In Postman I was getting the same error and it was fixed when I added a header:
      Content-Length: 100 (any value works here)

Here is the CONNECTIONJSON and the error in a target application:

EIC1.PNG

 

 

{
"authentications": {
"login": {
"properties": {
"PASSWORD": "***",
"REQUESTPARAMS": {
"Content-Length": "100",
"Content-Type": "application/soap+xml;charset=UTF-8"
},
"REQUESTXML": "<soap:Envelope xmlns:soap=\"http://www.w3.org/2003/05/soap-envelope\"><soap:Body></soap:Body></soap:Envelope>",
"SOAP_ENDPOINT": "https://***/sap/bc/srt/scs/sap/grac_user_acces_ws?sap-client=110"
"USERNAME": "***"
}
}
}
}

 

 

SAP1.PNG
Here are Postman and SOAP UI screenshots with successful responses:

Postman1.PNGPostman2.PNGSOAPUI1.PNGSOAPUI2.PNG

Could you please help identify the cause of the issue? Does Saviynt support XML body in the CONNECTIONJSON?

Any insights, experiences, or recommendations would be greatly appreciated. Thanks in advance for sharing your knowledge!

I was trying also to call without a body, but still errors:

  1. Removing an XML body in SOAP UI - there will be the same error "Wrong Content-Type and empty HTTP-Body received"
  2. Removing an XML body in Postman - Time-Out error.
  3. Removing RequestXML from ConnectionJSON in Saviynt - Time-out error

#SOAP

Best regards,
Olesia

[This message has been edited by moderator to merge reply comment]

3 REPLIES 3

SB
Saviynt Employee
Saviynt Employee

are you getting the error when trying to save and test the connection or is the error occurring on performing any provisioning operation.


Regards,
Sahil

Olesia
Regular Contributor
Regular Contributor

Hi @SB 

The error appears when I save the connection and it doesn't matter if REQUESTXML is included or not - the error is the same.

In SOAP UI if I clear the body, then there is the same 500 Internal Server Error. With an empty body (attached below), the response is 200 OK.

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
   <soap:Body/>
</soap:Envelope>

 

Olesia
Regular Contributor
Regular Contributor

Hi,

I managed to get it working by using TEST_URL parameter with WSDL URL like

https://***/sap/bc/srt/scs/sap/grac_user_acces_ws?sap-client=110&WSDL

While the SOAP_ENDPOINT URL is 

https://***/sap/bc/srt/scs/sap/grac_user_acces_ws?sap-client=110

I was referring https://forums.saviynt.com/t5/saviynt-knowledge-base/how-to-perform-save-and-test-connection-in-soap...