Follow this task to use a single built-in, file-based repository
in a new configuration under Federated repositories.
Before you begin
To use the default configuration under Federated repositories
that includes a single built-in, file-based repository only, you need
to know the primary administrative user name of the user who manages WebSphere® Application Server resources
and user accounts.
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.
- Optional: Leave the Realm name field value
as defaultWIMFileBasedRealm.
- 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 OK.
- 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, complete the following steps:
- Supply a password for the administrative user in the
Password field.
- Confirm the password of the primary administrative user
in the Confirm password field.
- Click OK.
- To modify the settings of the built-in, file-based repository, under Related items, click
Manage Repositories and then click the InternalFileRepository link.
- Salt length
- Specifies the salt length of the randomly generated salt for password hashing.
- Message digest algorithm
- Specifies the message digest algorithm to use for hashing the password.
- Key length
- Specifies the to-be-derived key length when PBKDF2 algorithms are used for password
hashing.
- Hash iterations
- Specifies the number of iterations to do for password hashing when PBKDF2 algorithms are
used.
- 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.
- 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
.
- 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
.
- 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
.
Results
After completing these steps, your new configuration under
Federated repositories includes a single built-in, file-based repository
only.
What to do next
- Before you can manage this account with Users and Groups, configure
supported entity types as described in Configuring supported entity types in a federated repository configuration.
- 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,
your federated repositories configuration is not used by WebSphere Application Server.
- If you are enabling security, complete the remaining steps, as
specified in Enabling security for the realm. As the final step,
validate this setup by clicking Apply in the Global security
panel.
- Save, stop, and restart all the product servers (deployment managers,
nodes, and Application Servers) for changes in this panel to take
effect. If the server comes up without any problems, the setup is
correct.