Follow this task to add a file-based repository under federated
repositories.
Procedure
- In the administrative console, click Security > Global
security.
- 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.
- Enter the name of the realm in the Realm name field.
You can change the existing realm name.
- Enter the name of the primary administrative user in the Primary
administrative user name field, for example, adminUser.
- Leave the Ignore case for authorization option selected.
- Leave the Allow operations if some of the repositories
are down option cleared.
- 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.
- Click Add base entry to realm.
- 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.
- Enter the distinguished name of the base entry within the
repository in the Distinguished name of a base entry in this repository field.
- Click Add > File repository.
- 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. The default value is 12.
- 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. The default value is SHA-1.
- 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.
- 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.