Set a single, LDAP repository in a new configuration under Federated repositories


Follow this task to configure a single, LDAP repository in a new configuration under Federated repositories.

To configure an LDAP repository in a new configuration under Federated repositories, 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. We can choose any valid user in the repository that is searchable. In some LDAP servers, admin users are not searchable and cannot be used (for example, cn=root in SecureWay). This user is referred to as the WAS administrative user name or administrative ID in the documentation. Being an admin 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 admin console after you turn on security. Use other users to log in, if those users are part of the administrative roles.

 

  1. In the admin console, click...

      Security | Global security

  2. Under User account repository, select Federated repositories from the Available realm definitions field and click Configure.

  3. On the Federated repositories panel...

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

    2. Enter the name of the primary admin user in the Primary administrativeistrative user name field, for example, adminUser.

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

    4. Click Add base entry to realm to add a base entry that uniquely identifies the external repository in the realm. Then complete the steps in Add an external repository in a federated repository configuration.

  4. On the Federated repositories panel...

    1. Select the built-in, file-based repository in the collection, and click Remove. Restriction: Before you remove the built-in, file-based repository from the admin realm, verify that at least one user in another member repository is a console user with administrative rights. Otherwise, disable security to regain access to the admin console.

    2. Click OK.

 

Results

After completing these steps, the new configuration under Federated repositories includes a single, LDAP repository only.

 

Next steps

  1. Before we can manage this account with Users and Groups, configure supported entity types

  2. After configuring the federated repositories, click Security > Global secuity 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 WAS.

  3. If enabling security, complete the remaining steps as specified in Enable security for the realm. As the final step, validate this setup by clicking Apply in the Global security panel.

  4. Save, stop, and restart all WAS servers (dmgrs, nodes and Application Servers) for changes in this panel to take effect. If the server comes up without any problems, the setup is correct.

 

Related tasks


Enable security