Symptom
It is found that SAP Web Dispatcher cannot trust the backend server certificate because it compares the server certificate information with a hostname different from the hostname used to call the backend destination. It is also found that in SAP Web Dispatcher profile parameter wdisp/ssl_certhost is manually set. And the hostname used to compare the server certificate information is the same that it is found in parameter wdisp/ssl_certhost .
Below is the error messages that can be found in Web Dispatcher trace:
*** ERROR => SSL handshake with <hostname called>:<port called> failed: SSSLERR_SERVER_CERT_MISMATCH (-30)
Server certificate not valid for supplied TargetHostname (fatal rfc2818 section 3.1 mismatch)
SapSSLSessionStartNB()==SSSLERR_SERVER_CERT_MISMATCH
TLSextSNI srv_name = "hostname set in wdisp/ssl_certhost"
TargetHostname = "hostname set in wdisp/ssl_certhost"
ServerCert.subject = <CN=hostname called,...>
ServerCert.issuer = <CN=...>
ServerCert.SANs = dNSName=<hostname called,...>
SSL NI-hdl 65: local=<local IP>:<client port> peer=<destination IP>:<Destination port>
{00000001} [icxxconn.c 3677]
HDB_KJE: <URL called>
peer certificate: SUBJECT="CN=<server certificate information>"
role: Client, protocol: HTTPS, local: <local IP>:<client port>, peer: <destination IP>:<Destination port>, id: 0/1, SNI:
Target Hostname="hostname set in wdisp/ssl_certhost"
Read more...
Environment
SAP Web Dispatcher
Keywords
wdisp/ssl_certhost, SSSLERR_SERVER_CERT_MISMATCH, wrong hostname certificate comparison, TargetHostname during ssl validation is wrong , KBA , BC-CST-WDP , Web Dispatcher , 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.
SAP Knowledge Base Article - Preview