Symptom
You would like to setup “Monitoring Access Host” of SAP Cloud Connector (SCC) in Solution Manager (SOLMAN) System's (SOLMAN Java stack) Managed System Configuration. Following symptoms can be experienced:
- An SSL/TLS connection to SAP Cloud Connector server from the SOLMAN Java stack fails with "handshake failure":
"Unable to open SSL connection to host [<SCC's hostname>:<port>]. Peer sent alert: Alert Fatal: handshake failure."
- An SSL trace with IAIK debug records (see SAP KBA 2673775) of the SOLMAN Java stack shows the following trace entries:
[...]
ssl_debug(1): Starting handshake (iSaSiLk 5.2)...
ssl_debug(1): Sending v3 client_hello message to <SCC's hostname>:8443, requesting version 3.3...
ssl_debug(1): Sending extensions: renegotiation_info (65281), signature_algorithms (13)
ssl_debug(1): Received alert message: Alert Fatal: handshake failure
ssl_debug(1): SSLException while handshaking: Peer sent alert: Alert Fatal: handshake failure
[...]
Read more...
Environment
- SAP NetWeaver Application Server Java
- Solution Management System
- SAP Cloud Connector
Product
Keywords
cipher suites, no cipher suites in common, TLS Alert, handshake failure, 400, null, 400 - 0, null -, javax.net.ssl.SSLHandshakeException, SSLHandshakeException , KBA , BC-JAS-SEC-CPG , Cryptography , SV-SMG-MON-ALR , Monitoring/Alerting/Reporting Infrastructure , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , SV-SMG-INS-CFG-MNG , Managed System Configuration , 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.