Symptom
During LDAP based authentication for the SAP Cloud Connector, the server logs indicate a failure with a "CERTIFICATE_UNKNOWN" message.
====
2024-20xx-xx-xx xx:xx:xx,xxx +0200#INFO#com.sap.scc.tomcat.utils.SystemPrintStreamSSLWrapper#https-jsse-nio2-8443-exec-6# #javax.net.ssl|FINE|16|https-jsse-nio2-8443-exec-6|20xx-xx-xx xx:xx:xx.xxx CEST|CertificateMessage.java:364|Consuming server Certificate handshake message (
20xx-xx-xx xx:xx:xx,xxx +0200#INFO#com.sap.scc.tomcat.utils.SystemPrintStreamSSLWrapper#https-jsse-nio2-8443-exec-6# #javax.net.ssl|SEVERE|16|https-jsse-nio2-8443-exec-6|20xx-xx-xx xx:xx:xx.xxx CEST|TransportContext.java:362|Fatal (CERTIFICATE_UNKNOWN): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (
"throwable" : {
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
====
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Read more...
Environment
- SAP Cloud Connector(SCC);
- Third-party LDAP Server.
Product
Keywords
SAP Cloud Connector, LDAP, Authentication, Invalid Certification Path, Certificate, JDK Secure Storage, Public Key, SCC Trust Store, Certificate handshake, PKIX path building failed, CERTIFICATE_UNKNOWN, cert, certificates, TLS, inspection, TLS-inspection, interception, intercept , 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.
SAP Knowledge Base Article - Preview