CO_CODERINT_CONNECTIVITY_CHECK: Ping result ICM_HTTP_SSL_PEER_CERT_UNTRUSTED

[floriangu]

Dear experts,

I have set up a logical default port in SOAMANAGER to configure the consumer proxy CO_CODERINT_CONNECTIVITY_CHECK to test the end2end connection ERP -> CPI -> C4C

However when trying a ping I get the following error:

SRT Framework exception: Service Ping ERROR: Error when calling SOAP Runtime functions: SRT: Processing error in Internet Communication Framework: ("ICM_HTTP_SSL_PEER_CERT_UNTRUSTED")

Strang thing is that the CPI certificates are imported into STRUST. A connection test for SM59-connections to CPI is also successful so a trusted connection obviously is established.

Still I am getting this error in SOAMANAGER.

Do you have any idea how to resolve this?

Thank you!

[ShivanandBH]

Dear Florain,

By any chance are you using certificate base authentication from ERP to CPI?, if so could you please verify whether have you uploaded the Issuer certificate of your ERP client certificate.

And may be you are using user based authentication in RFC destinations?

Regards,

Shivanand B H

[floriangu]

Hello,

thank you for your reply. Actually we are using basic authentication in the SM59 connection as well as in the logical port of the consumer proxy (Consumer Security -> Authentication Settings User ID / Password).

It seems that the server certificate is not trusted though - which is strange as it is imported into STRUST and the connection via SM59 to the same CPI-Tenant is working fine.

[ShivanandBH]

Hi Florian,

Another difference between E2E connection check and SM59 RFC connection check is that,

E2E connection check works from ERP to C4C via HCI, so may be the error is coming between HCI and C4C.

On the other hand RFC connection check is only from ERP to HCI.

Regards,

Shivanand B H