Symptom
- Principal propagation is not working from BTP to backend system via cloud connector
- Upon analysis of the ICM traces and Cloud Connector SSL traces, it is identified that the cloud connector is not forwarding it's system certificate to the ICM
- The following message is found in the ljs_trace with SSL trace enabled:
#*** ServerHelloDone
#Warning: no suitable certificate found - continuing without client authentication
#*** Certificate chain
#<Empty>
#***
(* or similar message indicating the handshake will continue without client authentication:
"No X.509 certificate for client authentication, use empty Certificate message instead".
The exact message depends on the SCC release.)
Read more...
Environment
SAP Cloud Connector
Product
connectivity proxy for SAP Connectivity service all versions
Keywords
client did not send any cert, <no cert>, PP, icm/trusted_reverse_proxy_0 , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.