Self Service Password Reset allows you to configure multiple LDAP directory profiles. If you are manually configuring Self Service Password Reset, you must create an LDAP directory profile. For more information, see Creating an LDAP Profile for Your Environment.
You can have more than one LDAP directory profile depending on your environment. Each LDAP profile defines a unique LDAP data environment that depends on the directory type and configuration. Each profile can have multiple redundant servers defined that must be shared on all the servers.
NOTE:You can either use Active Directory or eDirectory for an instance of Self Service Password Reset configuration.
To configure LDAP profiles:
Log in to Self Service Password Reset at https://dns-name/sspr as an administrator.
In the toolbar, click your name.
Click Configuration Editor > LDAP > LDAP Directories > default.
(Conditional) If you want to create different profiles for a different set of users:
Click Edit List, then add the profile names to the list by using Add Profile.
In the Add Value field, enter the profile name.
The profile name must have the following format:
Start with a letter (a-Z)
Contain only letters, numbers, and hyphens
Length between 2 and 15 characters
You can include multiple profiles. During authentication, Self Service Password Reset searches for the default profile first, and then the other profiles in the order mentioned.
Self Service Password Reset does not allow changing the name of the profile but you can change the display name of the profile for the users.
Select the appropriate profile from the Selected Profile list.
Configure the following settings:
Specify the URLs of LDAP servers.
The system uses these servers in configuring failover in the same order as these appear in this list. If the first server is unavailable, the system uses the next available server in the list. Self Service Password Reset checks unavailable servers periodically to check their availability.
For secure SSL, use the ldaps://servername:636 format. For plain text servers, use the ldap://serverame:389 format (not recommended). When using secure connections, the Java virtual machine (JVM) must trust the directory server in either of these scenarios:
It has a valid commercial certificate.
You have manually added the public key certificate from the tree to the Java keystore.
IMPORTANT:
Do not use a non-secure connection for anything but the most basic testing purposes (Many LDAP servers will reject password operations on non-secure connections)
Do not use a load-balancing device for LDAP high availability, instead use the built-in LDAP server fail-over functionality
Do not use a DNS round-robin address.
Displays details of LDAP server certificates. Click Import From Server to import the certificates from the server.
Configure an LDAP proxy user in the LDAP distinguished name format. For example, cn=admin,o=example or cn=administrator,cn=users,dc=subdomain,dc=domain,dc=net
You can gain access to the LDAP directory through the LDAP proxy user. This user must have the following rights:
Browse users and manage password attributes of the user object
Create object rights in the new user container (if enabled)
Set a password for the LDAP proxy user.
Specify the base context to search for user names during authentication and other operations. This is the top level LDAP container in which your users exist.
You can add multiple contexts. Self Service Password Reset searches each context until it finds a single match. To improve search performance, do not add large numbers of contexts because Self Service Password Reset searches each context serially.
Specify an LDAP test user account. Create a new test user account with the same privileges and policies as any other users in the system. You can change the password of this account and use it periodically to check the health of the LDAP server.
Using a test user account increases the ability to detect and alert you to any configuration or health issues. Use a test user to test the following:
Authentication
Read password policy
Set password
Set challenge-responses
Load challenge-responses
This is an important setting. You can configure an LDAP Test User DN later also.
Specify the LDAP object classes to automatically add users who are authenticated using the password servlet. This is an auxiliary LDAP class that contains attributes used to store password self-service data. If you extended the schema to store the challenge-response information, this setting is required This is not required for Active Directory even with schema extension
Specify the user name search query in the following format:
(&(objectClass=person)(cn=%USERNAME%))
Replace the value %USERNAME% with the actual user name value. Self Service Password Reset uses this filter for the contextless login and for finding users in the LDAP directories.
Specify an attribute to allow pages to display other details such as the user name of a user instead of the LDAP Naming Attribute value.
Select this option to create a unique GUID value and assign it to any user who does not have a GUID value and is attempting to authenticate. The system writes this value to the attribute named in the LDAP GUID Attribute setting.
Specify an attribute to identify and reference unique users in the LDAP directory. You can set any string readable attribute as the GUID, as long as the directory can be trusted to the uniqueness. You can also use a custom attribute and enable Auto-Add GUID Value.
The default value is VENDORGUID. For the default value, the system attempts to read the vendor-specific LDAP GUID.
Specify the values in this format: display value:::context. For example,
ou=sf,ou=ca,o=example:::San Francisco
ou=lon,ou=uk,o=example:::London
ou=nyc,ou=ny,o=example:::New York
This is an optional setting. If you configure this, the system adds a field to the form-based login screen and other user search screens. This field allows users to select a specific context.
Specify an attribute name that the system can use as the naming attribute on LDAP user entries. This attribute is the first part of the distinguished name of a user. This name is constant depending on the directory vendor type even if you use a different attribute for the login search filter. Typically, the naming attribute is cn or uid.
Specify an attribute to record when users update their passwords and when the system uses the password during replication checks and other processes.
Specify the attribute for a user entry that you specified as a group entry in the directory.
Specify the name of the LDAP profile that you have configured. Self Service Password Reset displays this name to the users.
Select Enabled if you want to enable this profile. When you deselect this option, the system disables the profile but does not delete the configuration details of the settings. This setting is helpful when you do not want to remove all the configuration settings for a particular profile but keep the profile for future use.
Click Test LDAP Profile to test if Self Service Password Reset is able to read the data of the users in a specific profile.
Click Save changes.