Configure a single built-in, file-based repository and one or more LDAP repositories in a federated repository configuration

To configure a built-in, file-based repository in a federated repository configuration, we must know the primary administrative user name of the user who manages WebSphere Application Server resources and user accounts.

To configure an LDAP repository in a federated repository configuration, have a user name (ID), the user password, the server host and port and, if necessary, the bind distinguished name (DN) and the bind password. We 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 in to the administrative console after turning on security. Use other users to log in if those users are part of the administrative roles.

Tasks

1. In the administrative console, click Security > Global security.

2. 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.

3. Enter the name of the realm in the Realm name field. We can change the existing realm name.

4. Enter the name of the primary administrative user in the Primary administrative user name field, for example, adminUser.

   Restriction: When we configure multiple repositories that includes a single built-in, file-based repository, the primary administrative user name must exist in the file-based repository. If the primary administrative user name does not exist in the file-based repository, then the name is created in the file-based repository. The primary administrative user name cannot exist in other repositories.

5. Select the Ignore case for authorization option.

   When the realm includes a built-in, file-based repository, enable the Ignore case for authorization option. When we 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.

6. 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.

7. 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.

8. Optional: Click Add base entry to realm if the LDAP repository needed is not contained in the collection. Then complete the steps in Add an external repository in a federated repository configuration.

9. On the Federated repositories panel:

   1. Optional: Repeat step 6 if the LDAP repository needed is not listed in the collection.

   2. Click Use built-in repository if the built-in, file-based repository is not listed in the collection.

   3. Optional: Select the repositories in the collection that we do not need in the realm and click Remove.

      Restriction: The realm must always contain at least one base entry; therefore, we cannot remove every entry.

   4. Click OK.

10. Provide an administrative user password. This panel displays only when a built-in, file-based repository is included in the realm. Otherwise, the panel does not display. If a built-in, file-based repository is included:
    1. Supply a password for the administrative user in the Password field.
    2. Confirm the password of the primary administrative user in the Confirm password field.

    3. Click OK.

After completing these steps, the federated repository configuration, which includes a single built-in, file-based repository and one or more LDAP repositories, is configured.

What to do next

1. Before we can manage this account with Users and Groups, configure supported entity types as described in Configure supported entity types in a federated repository configuration.

2. After configuring the federated repositories, click Security > Global security to return to the Global security panel. Verify that Federated repositories is identified in the Current realm definition field. If Federated repositories is not identified, select Federated repositories from the Available realm definitions field and click Set as current. To verify the federated repositories configuration, click Apply on the Global security panel. If Federated repositories is not identified in the Current realm definition field, the federated repositories configuration is not used by WebSphere Application Server.

3. If we are enabling security, complete the remaining steps as specified in Enable WebSphere Application Server security. As the final step, validate this setup by clicking Apply in the Global security panel.
4. Save, stop, and restart all the product servers (deployment managers, nodes, and Application Servers) for changes in this panel to take effect. If the server comes up without any problems, the setup is correct.