!--a11y-->
Defining an LDAP Directory as a Data
Source 
Use the user management configuration tool to provide the details required to connect to an LDAP directory.
To provide high availability of the LDAP data source, you can configure user management for more than one LDAP server. In this case, you cannot use the configuration tool, instead you must change the user management properties directly. For more information, see Configuring High Availability of the LDAP Data Source.
For more information on defining an LDAP directory as a data source, see Configuring UME to Use an LDAP Server as Data Source.
See LDAP Directory as Data Source.
...
1. Start the user management configuration tool by choosing System Administration ® System Configuration ® UM Configuration.
2. Choose the LDAP Server tab
3. Enter data in the fields as follows:
Field Name |
Field Data |
Server Name |
Host on which the directory server is located. |
Port |
Port of the LDAP directory server. |
User |
Distinguished name (DN) of user that is used to connect (bind) to the LDAP directory server.
cn=Directory Manager |
Password |
Password of the user specified above. |
User Path |
Distinguished name of branch of directory where information about users is stored.*
|
Group Path |
Distinguished name of the branch of your directory where information about the groups of portal users is stored.*
|
* If you have a ‘groups in a tree’ hierarchy, the User Path and Group Path fields must have the same value.
4. If you wish to set up a secure connection to the corporate LDAP directory, select Use SSL for LDAP access.

For more information on setting up a secure connection, see the section on Secure Communications in the SAP Enterprise Portal Security Guide. You can find the Security Guide on SAP Service Marketplace.
5. To test the connection to the LDAP directory, choose Test Connection.
6. Choose Save to save the entire configuration (that is, data from all the tabs). Otherwise choose Reset to undo all data you have entered on this tab.

After changing settings using the configuration tool, you must restart the Java application server for the changes to take effect.
