Add a file-based repository to a federated repositories configuration

Follow this task to add a file-based repository under federated repositories.

1. In the 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. We 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

    Unique identifier for the repository. This identifier uniquely identifies the repository within the cell.

    Repository adapter class name

    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

    Salt length of the randomly generated salt for password hashing. The default value is 12.

    Message digest algorithm

    Message digest algorithm to use for hashing the password. Select one of the following: SHA-1, SHA-256, SHA-384 or SHA-512. The default value is SHA-1.

    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.

13. Click OK and Save to the master configuration.

Results

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

Related tasks

Enable client certificate login support for a file-based repository in federated repositories