Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository
Configure multiple LDAP repositories in a federated repository
- Choose any searchable user in LDAP to serve as the WAS administrative user. With some LDAP servers, for example, cn=root in SecureWay, admin users are not searchable. This user ID and password are used to log into the admin console after global security is enabled. We can use other users as long as they belong to administrative roles.
- Click...
Security | Global security | User account repository | Available realm definitions | Federated repositories | Configure
To configure for a specific domain in a multiple security domain environment, click...
Security domains | domain_name | Security Attributes | User Realm | Customize for this domain | Realm type | Federated repositories | Configure
- The realm in the Realm name field. We can change the existing realm name.
- The primary administrative user in the Primary administrative user name field, for example, adminUser.
- 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 Add an external repository in a federated repository.
- On the Federated repositories panel...
- Optional: Repeat step 6 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, disable security to regain access to the admin console.
- Click OK.
Results
After completing these steps, your federated repository, which includes multiple LDAP repositories, is configured.
What to do next
- Before you can manage this account with Users and Groups, configure supported entity types as described in Configure supported entity types in a federated repository.
- 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, your federated repositories configuration is not used by WAS.
- If you are 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.
- Save, stop, and restart all the product 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.