Follow this task to change
your federated repository configuration
to include a single built-in, file-based repository only.
Before you begin
To change your federated
repository configuration to include a single
built-in, file-based repository only, you need to know the primary
administrative
user name of the user who manages WebSphere
® Application
Server resources
and user accounts.
Restriction: Client certificate login
is not
supported in a realm that includes a single built-in, file-based repository
or a single built-in, file-based repository with other repositories.
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.
- Enter the name of the realm in the Realm name field.
If the realm
contains a single built-in, file-based repository only, you must specify defaultWIMFileBasedRealm as
the realm name.
- Enter the name of the primary
administrative user in the Primary
administrative user name field, for example, adminUser.
- Enable the Ignore case for authorization option.
- Click Use built-in repository if the built-in,
file-based
repository is not listed in the collection.
- Select
all repositories in the collection that are not of type
File and click Remove.
- Click OK.
- Provide an administrative user password. This
panel
displays only when a built-in, file-based repository is included in
the realm.
Otherwise, it does not display. If a built-in, file-based repository
is included,
complete the following steps:
- Supply
a password for the primary administrative user in the
Password field.
- Confirm the password
of the primary administrative user in the
Confirm password field.
- Click OK.
Results
After completing these
steps, your federated repository configuration,
which includes a single built-in, file-based 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.