Error when fetching via API call in CAI

[former_member730006]

Hi Everyone,

I was trying to connect the SAP CAI to an On-Premise S/4HANA System. I am using a global account for SAP Cloud Platform and accessed the Enterprise edition of CAI. I used a cloud connector to connect to backend ABAP system and created a destination with the virtual host in SAP Cloud platform. But when I am trying to fetch the destination via API call in CAI, it throws me the following error, in spite of configuring all the connections in Cloud connector and in destinations with HTTP.

{"api_service_response": { "body": "HTTPS proxying is not supported. Use HTTP instead. HTTPS is not needed because communication is already secured by the tunnel. ", "status_code": 405 } }

Could you please suggest a solution to resolve this?

[JonasB]

Hi Madhumitha,

when using an SAP Cloud Connector, the URL maintained in the destination should not start with https:// but rather with http:// and also the virtual host in the cloud connector should be configured accordingly. HTTPS is security-wise not required here, as the connection is anyway secured with a tunnel, as mentioned in the error message.

Regards
Jonas

[former_member730006]

Hi Jonas,

The protocol used in Cloud connector is HTTP and used http://<virtualhost>:<virtual port> in the URL in Destination in cloud platform. Still the error persists.

[JonasB]

Hi Madhumitha,

could you provide a screenshot of the destination?

Nevertheless this issue is not related to SAP Conversational AI, but rather to the SAP Cloud Connector and destination service.

Regards
Jonas

[JonasB]

Hi Madhumitha,

please post a screenshot of the destination as well as the Cloud Connector configuration.

Regards
Jonas

[roy_pappachan2]

Hi Madhumitha,

You can check the URI https://<...><port>/sap/opu/odata/. from gateway itself.

Thanks,

Roy

[roy_pappachan2]

Hi Madhumita,

Please check your destination Destination Configuration in cockpit.

"Type" should be "HTTP"

"URL" will be https://<...>;

Thanks,

Roy

[former_member730006]

Hi Roy,

I have configured it in the same approach, still the error persists. Any Idea if it is because of authentication issue and do I need to configure Principal Propagation for authentication?

Thanks,

Madhumitha

[former_member192050]

Hi Madhumita,

I think you are trying to call the API with HTTPS(protocol) which may causing the error
just try to call the same API from your web browser using HTTP.

Thanks,

Sathish.