Configuring multiple Lightweight Directory Access Protocol repositories in a federated repository configuration
To configure an LDAP repository in a federated repository configuration, you must know a valid user name (ID),
the user password, the server host and port and, if necessary, the bind distinguished name (DN) and the bind
password. You can choose any valid user in the repository that is searchable. In some LDAP servers,
administrative users are not searchable and cannot be used (for example,
cn=root in SecureWay).
This user is referred to as a WebSphere Application Server administrative user name or
administrative ID in the documentation. Being an administrative ID means a user has
special privileges when calling some protected internal methods. Normally, this ID and password are used to
log into the administrative console after you turn on security. You can use other users to log in if those
users are part of the administrative roles.
In the administrative console, click Security > Global security.
Under User account repository, select Federated repositories from the Available realm definitions field and click Configure....
To configure for a specific domain in a multiple security domain environment, click Security domains > domain_name. Under Security Attributes, expand User Realm, and click Customize for this domain. Select the Realm type as Federated repositories and then click Configure.
Enter the name of the realm in the Realm name field. You can change the existing realm name.
Enter the name of the primary administrative user in the Primary administrative
user name field, for example,
Optional: Select the Ignore case for authorization option. When you enable this option, the authorization check is case-insensitive. Normally, an authorization check involves checking the complete DN of a user, which is unique in the realm and is case-insensitive. Clear this option when all of the member repositories in the realm are case-sensitive.
Restriction: Some repositories contain data that is case-sensitive only, and some repositories contain data that is case-insensitive only. Do not include both case-sensitive and case-insensitive repositories in the realm. For example, do not include case-sensitive repositories in the realm with a built-in, file-based repository.
Optional: Select the Allow operations if some of the repositories are down option to allow operations such get or search even if the repositories in the realm are down:
Optional: In a multiple security domain environment, select Use global schema for model option to indicate that the global schema option is enabled for the data model. Global schema refers to the schema of the admin domain.
Optional: Click Add Base entry to Realm... if the LDAP repository that you need is not listed in the collection. Then complete the steps in Adding an external repository in a federated repository configuration.
On the Federated repositories panel, complete the following steps:
Optional: Repeat step 8 if the LDAP repository that you need is not listed in the collection.
Optional: Select the repositories in the collection that you do not need in the realm and click Remove. The following restrictions apply:
The realm must always contain at least one base entry; therefore, you cannot remove every entry.
If you plan to remove the built-in, file-based repository from the administrative realm, verify that at least one user in another member repository is a console user with administrative rights. Otherwise, you must disable security to regain access to the administrative console.
After completing these steps, your federated repository configuration, which includes multiple LDAP repositories, is configured.