Follow this task to change your federated repository configuration
to include a single, Lightweight Directory Access Protocol repository
(LDAP) repository only.
Before you begin
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.
Procedure
- 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, 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.
- Leave the Allow operations if some of
the repositories are down option cleared.
- 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 contained 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: Select the repositories in the
collection that you do not need in the realm and click Remove.
Restriction: The realm must always contain at least
one base entry; therefore, you cannot remove every entry.
- Click OK.
Results
After completing these steps, your federated repository configuration,
which includes a single LDAP repository only, is configured.
What to do next
- Before you can manage this account with Users and Groups, configure
supported entity types as described in Configuring supported entity types in a federated repository configuration.
- 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 WebSphere Application Server.
- If you are enabling security, complete the remaining steps as
specified in Enabling 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 (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.