Adding a file-based repository to a federated repositories configuration

Follow this task to add a file-based repository under federated 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. To configure for a specific domain in a multiple security domain environment, click Security domains > domain_name. Under Security Attributes, expand User Realm, and click Customize for this domain. Select the Realm type as Federated repositories and then click Configure.
  3. Enter the name of the realm in the Realm name field. You can change the existing realm name.
  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 selected.
  6. Leave the Allow operations if some of the repositories are down option cleared.
  7. 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.
  8. Click Add base entry to realm.
  9. Enter a distinguished name for the realm base entry in the Distinguished name of a base entry that uniquely identifies this set of entries in the realm field.
  10. Enter the distinguished name of the base entry within the repository in the Distinguished name of a base entry in this repository field.
  11. Click Add > File repository.
  12. Specify the required details for the new file repository:
    Repository identifier
    Specifies a unique identifier for the repository. This identifier uniquely identifies the repository within the cell.
    Repository adapter class name
    Specifies the implementation class name for the repository adapter. For a file repository, leave it as com.ibm.ws.wim.adapter.file.was.FileAdapter.
    Base directory
    The base directory where the files are to be created. This directory must already exist.
    File name
    The file name for the repository. The default value is fileRegistry.xml.
    Salt length
    Specifies the salt length of the randomly generated salt for password hashing. Before V8.5.5.17, the default value is 12.

    [8.5.5.17 or later]The default value is 32.

    Message digest algorithm
    Specifies the message digest algorithm to use for hashing the password.

    Select one of the following: SHA-1, SHA-256, SHA-384, or SHA-512.

    [8.5.5.17 or later]Beginning with V8.5.5.17, you can also select PBKDF2WithHmacSHA1.

    Before V8.5.5.17, the default value was SHA-1.

    [8.5.5.17 or later]The default value is PBKDF2WithHmacSHA1.

    [8.5.5.17 or later]Key length
    Specifies the to-be-derived key length when PBKDF2 algorithms are used for password hashing. The default value is 32.
    [8.5.5.17 or later]Hash iterations
    Specifies the number of iterations to do for password hashing when PBKDF2 algorithms are used. Default value is 100000.
    Login properties
    Specifies the 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.
    [8.5.5.22 or later]Lockout threshold
    Specifies the number of unsuccessful attempts that a user is allowed before the account is locked. The default threshold is five unsuccessful attempts. To disable account lockout, set the account lockout threshold to 0.
    [8.5.5.22 or later]Lockout duration (minutes)
    Specifies the duration of time in minutes that the account is locked when the number of unsuccessful login attempts exceeds the accountLockoutThreshold value. The value for this attribute must be greater than zero if the accountLockoutThreshold attribute is set. The default value in minutes is 15.
    [8.5.5.22 or later]Ignore a failed login after (minutes)
    Specifies the duration of time in minutes that a single unsuccessful login attempt counts toward the account lockout threshold. All failed login attempts for the user account are also cleared after a successful login or after a password update. If the accountLockoutThreshold attribute is set, the value for this attribute must be greater than 0. The default value in minutes is 15.
  13. Click OK and Save to the master configuration.

Results

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