403 error handling in cpi

[dineshhome1361_7]

Hi Team,

Scenario: CPI to On-Premise OData API

Errors:

• com.sap.gateway.core.ip.component.odata.exception.OsciException: HTTP Request failed with error : Read timed out (local port XXXXX to address X.X.X.X (<msgid>), remote port YYYYY to address Y.Y.Y.Y (ip-x-x-x-x.eu-central-1.compute.internal)), cause: java.net.SocketTimeoutException: Read timed out
• com.sap.gateway.core.ip.component.odata.exception.OsciException: Forbidden : 403 : HTTP/1.1

I have a basic idea that 403 means it is firewall issue and it needs IP whitelisting from the target side. Could anyone explain from CPI perspective what is the resolution to fix above errors if anyone had worked on these issues?

Thanks,

Dinesh

[former_member724290]

If this is an error when sending, then check the user you are sending. He must have the rights in the cockpit to send. Or is it a mistake at the sending step in on-premises?

[former_member813012]

Error – http status 403 – forbidden SAP CPI. Cause – You are using CSRF Protected authorization in connection parameter. Resolution – Disable / uncheck the CSRF Protected check box under the HTTPS adapter connection. You can also check the demo in our latest video.

Regards,
J Wick

[dineshhome1361_7]

Hi Jimmy,

You have mentioned about the HTTPS sender adapter but my scenario is OData where this was checked while posting and we didn't face any issue in non-production but in production it was failing with 403 at initial loads.

Thanks,

Dinesh

[1514384]

Still I am facing the 403 forbidden error in postman