Delete the default data store.
Create a new data store.
Click New .
In the “Step 1 of 2: Select Type of Data Store” page, set the following attributes:
Choose “LDAPv3 Repository Plug-In.”
In the “Step 2 of 2: New Data Store” page, set the following attributes:
In the Add field, enter the hostname and port number for the existing directory. Use the form LoadBalancer-2.example.com:489
Select the default DirectoryServer-1.example.com:1389 , and then click Remove.
Enter uid=userdbadmin,ou=users,dc=company,dc=com .
When this field is empty, the search for users will start from the root suffix.
These values were imported into the user data store in a previous task. See To Import Users into the User Data Store.
Click Finish and log out of the Access Manager console.
Restart each Access Manager server for the changes to take place.
Log in to each Access Manager host system, and restart the Web Server on each host system.
Verify that in the Access Manager console you can see the users in the external user data store.
Go to the Access Manager URL.
Log in to the Access Manager console using the following information:
Click on Users Realm.
Click on Subjects tab.
You should see three new users: authuiadmin, userdbadmin, and userdbauthadmin.
Verify that a user can successfully authenticate against the new realm.
Start a new browser session and log in to Access Manager.
Go to the following URL:
The parameter realm=users specifies the new realm to use for authentication. Without the parameter, the default realm is used.
On the login page, provide a user login and password from the existing directory.
You should be able to log in successfully.
If the login is not successful, watch the existing Directory Server access log to troubleshoot the problem.
At this point, a user can log in against the existing Directory Server if he invokes the realm=users parameter. If such a parameter is absent, the default realm is used.
Administrators who want to access the Access Manager console should log in to the default realm.