In the server configuration, you can designate a repository administrator from within the LDAP registry. After you enable LDAP integration within the server configuration, you cannot log on by using admin as the user ID and password.
After you edit the Custom User Registry settings, you must restart the server.
You must designate an administrator ID. If you do not set up a valid administrator ID, when you switch the container to use the external registry, you cannot log on to Rational Asset Manager by using the admin user ID and password and cannot configure the product.
To set up an administrator ID, click . Then, locate the Custom User Registry section and designate an administrator ID for a valid user in the external registry.
To set up your container to work with an LDAP registry:
Rational Asset Manager is configured to work with a generic LDAPUserInformationFactory class that connects to an LDAP v3 registry and that provides the user information API.
The default LDAPUserInformationFactory class is a generic LDAP user information factory that requires a specific configuration to search and retrieve users and groups. The following information explains each configuration.
Every user entry in Rational Asset Manager has an associated user ID, which comes from a user registry such as LDAP. If a user ID is no longer found in the LDAP registry, then the display name for the user entry in Rational Asset Manager is changed to append (Not found) to the name. No other changes are made to the user entry. For example, ownership of assets by a user ID that is not found is not changed. A user ID might not be found in the LDAP registry because the entire user entry was removed from the LDAP registry, or because the user ID was changed in the LDAP registry. If a user ID changes in the LDAP registry, and this user ID is used in Rational Asset Manager, a new user entry for the new user ID is created in Rational Asset Manager.