Changing a federated repository configuration to include a single built-in, file-based repository only

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

  1. In the administrative console, click Security > Global security.
  2. Under User account repository, select Federated repositories from the Available realm definitions field and click Configure.
  3. 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.
  4. Enter the name of the primary administrative user in the Primary administrative user name field, for example, adminUser.
  5. Enable the Ignore case for authorization option.
  6. Click Use built-in repository if the built-in, file-based repository is not listed in the collection.
  7. Select all repositories in the collection that are not of type File and click Remove.
  8. Click OK.
  9. 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:
    1. Supply a password for the primary 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 federated repository configuration, which includes a single built-in, file-based repository only, is configured.

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 > 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.
  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 Global security 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    

Terms of Use | Feedback

Last updated: Oct 20, 2010 7:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=twim_filebased_preconfig
File name: twim_filebased_preconfig.html