Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository


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


Overview

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

Know the primary administrative user name of the user who manages WAS resources and user accounts.

Client certificate login is not supported with this configuration.


Procedure

  1. In the admin console, click...

      Security | Global security | User account repository | Available realm definitions | Federated repositories | Configure

    To configure for a specific domain in a multiple security domain environment, click...

      Security domains | domain_name | Security Attributes | User Realm | Customize for this domain | Realm type | Federated repositories | Configure

  2. Leave the Realm name field value as...

      defaultWIMFileBasedRealm

  3. The primary administrative user in the Primary administrative user name field, for example, adminUser.

  4. Leave the Ignore case for authorization option selected.

  5. Leave the Allow operations if some of the repositories are down option cleared.

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

  7. Click OK.

  8. 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 administrative user in the Password field.

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

    3. Click OK.

  9. To modify the settings of the built-in, file-based repository, under Related items, click...

      Manage Repositories | InternalFileRepository

    Salt length

    Salt length of the randomly generated salt for password hashing.

    Message digest algorithm

    Message digest algorithm to use for hashing the password.

    Login properties

    Property names to use to log into the application server. This field takes in multiple login properties, delimited by a semicolon (;).

    Custom properties

    Specifies arbitrary name and value pairs of data. The name is a property key and the value is a string value that can be used to set internal system configuration properties.


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

      Available realm definitions | Federated repositories | Set as current

    To verify the federated repositories configuration, click Apply on the Global security panel. If Federated repositories is not identified in the field...

      Current realm definition

    ...your federated repositories configuration is not used by WAS.

  3. If you are enabling security, complete the remaining steps.

  4. Validate setup by clicking Apply in the Global security panel.

  5. Save, stop, and restart all the product 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.


Related


Administrative user password settings
Federated repository wizard settings

+

Search Tips   |   Advanced Search