Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Content is not allowed in prolog SOAP 403 error

RajeshA
Regular Contributor
Regular Contributor

Environment set up  Saviynt is acting as a ticketing tool to create tickets in SAPGRC as mentioned in https://forums.saviynt.com/t5/saviynt-knowledge-base/using-saviynt-as-a-ticketing-system-for-sap-grc...

Slight difference is Saviynt is not connected to SAPGRC directly, Saviynt is connected to middleware called SAP Integration Suite and SAP integration suite is connected to GRC. So all the communications between Saviynt and SAPGRC happens through SAP integration suite.

Middleware team had provided two urls as below

 

Issue

I am trying to create a account (you can see the xml being used in the logs) with one SAP role and seeing an error while provisioning. After researching multiple forums I am able to conclude there is no way we can see evaluated SOAP payload in logs. And I am seeing 403 error in logs.

How can troubleshoot this issue without seeing what is being sent to the server. 

2024-05-15/20:05:01.451 [{}] [quartzScheduler_Worker-9] ERROR provisoning.SoapProvisioningService - Error while creating account RAJEAVUL:
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.

[This message has been edited by moderator to mask url]

 

4 REPLIES 4

rushikeshvartak
All-Star
All-Star
  • You can access issue with service account.
  • does api works in postman if yes provide screenshot
  • share jsons

Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

RajeshA
Regular Contributor
Regular Contributor

Please remove hostname Keep company-specific private information masked on public forums, such as the name and URL.


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Looks like this is issue with network connectivity.

Steps to Resolve the HTTP 403 Forbidden Error

  1. Check Authentication Credentials:

    • Ensure that the credentials (username and password or API keys) used for the SOAP web service call are correct.
    • Verify that the credentials have the necessary permissions to access the web service.
  2. Verify Endpoint URL:

  3. Network and Firewall Settings:

    • Ensure that there are no network issues or firewall settings blocking access to the web service.
    • Check if there are any IP restrictions or whitelisting requirements for accessing the endpoint.
  4. SOAP Action Header:

    • Verify that the correct SOAP action is being used in the request header. Some web services require a specific SOAP action header to authorize the request.
  5. Access Control on Web Service:

    • Confirm that the web service itself is configured to accept requests from the client making the call. This could involve checking web service access control lists (ACLs) or settings on the web service provider.

Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.