Symptom
- The DataSource has been switched from Database to LDAP as per the official document provided by SAP
- After the above configuration, search any LDAP user, the search does not show any results and displays error message "No Element Found"
- Checked SAP KBA 2455540 - No Element found in NWA Identity Management and the solution is not valid for you.
- If Troubleshooting Wizard Traces are run with locations a) com.sap.security.core.persistence & b) com.sap.security.core.performance; it will be observed that search does not return anything. An entry like "Status after search is "0", result is "Size=0 []" will be seen.
- If compare TSHW traces and LDIF (LDAP administrators would be able to provide this traces based on the LDAP solution) traces for the same search query, it will be observed that the value of ume.ldap.access.base_path.user differs in both. For example, in TSHW traces, this value might be OU=ABC,DC=com and in LDIF traces show that the users are stored in DC=ABC,DC=com.
Read more...
Environment
SAP NetWeaver 7.1 and above
Product
SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3
Keywords
ume.ldap.access.base_path,AuthenticationException,No connection to the ldap server,LDAP Server configuration,Active Directory,Active Directory,private section,dataSourceConfiguration_<LDAP_directory_vendor>_not_readonly_db.xml,dataSourceConfiguration_<LDAP_directory_vendor>_deep_readonly_db.xml,Distinguished Names (DNs), IDM, IDM UI, UI, AdminUI , KBA , BC-JAS-SEC-UME , User Management Engine , 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.