Using a single built-in, file-based repository in a new configuration under Federated repositories

Follow this task to use a single built-in, file-based repository in a new configuration under Federated repositories.

Before you begin

To use the default configuration under Federated repositories that includes 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.
[Fix Pack 45 or later] Important:

By default, 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. To enable support for certificate mapping in the file-based repository, install WebSphere Application Server fixpack version 6.1.0.45 or higher, and follow the procedure in the topic, Enabling client certificate login support in a federated repositories file-based repository.

Procedure

  1. In the administrative console, click Security > Secure administration, applications, and infrastructure.
  2. Under User account repository, select Federated repositories from the Available realm definitions field and click Configure.
  3. Leave the Realm name field value as defaultWIMFileBasedRealm.
  4. Enter the name of the primary administrative user in the Primary administrative user name field, for example, adminUser.
  5. Leave the Ignore case for authorization option enabled.
  6. Click OK.
  7. 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, complete the following steps:
    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.

Results

After completing these steps, your new configuration under Federated repositories includes a single built-in, file-based repository only.

What to do next

  1. 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.
  2. After configuring the federated repositories, click Security > Secure administration, applications, and infrastructure to return to the Secure administration, applications, and infrastructure 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 Secure administration, applications, and infrastructure panel. If Federated repositories is not identified in the Current realm definition field, your federated repositories configuration is not used by WebSphere Application Server.
  3. 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 Secure administration, applications, and infrastructure 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.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 6:03:36 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-iseries&topic=twim_filebased_unconfig
File name: twim_filebased_unconfig.html