Use 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.

To use the default configuration under Federated repositories that includes a single built-in, file-based repository only, we need to know the primary admin user name of the user who manages WAS 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.

 

  1. In the admin console, click...

      Security | Global security

  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 admin user in the Primary administrativeistrative 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...

    1. Supply a password for the admin user in the field.

    2. Confirm the password of the primary admin user in the Confirm password field.

    3. Click OK.

 

Results

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

 

Next steps

  1. Before we can manage this account with Users and Groups, configure supported entity types.

  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, the federated repositories configuration is not used by WAS.

  3. If 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.

  4. Save, stop, and restart all WAS 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.


Administrative user password settings
Federated repository wizard settings