Symptom
SAP Cloud Connector (SCC) uses LDAP for Authentication.
Users such as sccadmin, sccsupport, sccmonitoring etc, are not able to access SCC WebUI login, and in the trace file (ljs_trace.log) below errors are perceived:
#DEBUG#org.apache.catalina.authenticator.FormAuthenticator#http-bio-8443-exec-8# #Authenticating username 'sccadmin'| DEBUG#org.apache.catalina.realm.CombinedRealm#http-bio-8443-exec-8# #Attempting to authenticate user "sccadmin" with realm "org.apache.catalina.realm.JNDIRealm/1.0"| DEBUG#org.apache.catalina.core.ContainerBase.[Catalina]#http-bio-8443-exec-8# #Connecting to URL ldap://<hostname>:389| #INFO#org.apache.catalina.core.ContainerBase.[Catalina]#http-bio-8443-exec-8# #Exception performing authentication. Retrying... javax.naming.CommunicationException: <LDAP hostname> [Root exception is java.net.ConnectException: Connection refused (Connection refused) |
Read more...
Environment
- SAP Cloud Connector(SCC) release independent;
- Linux Operating System;
- Windows Operating System.
Product
SAP Business Technology Platform all versions ; SAP Connectivity service 2.0
Keywords
ABAP, R/3, ERP, connection check, HTTPS connection, certificate, com.sap.scc.rt, SccEndpointValidator, system certificate, ssl, LDAP, authentication, unauthorized, 389 , 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.