Stand-alone custom registry settings

Use this page to configure the stand-alone custom registry.

To view this administrative console page, complete the following steps:

Click Security > Global security.
Under User account repository, click the Available realm definitions drop-down list, select Stand-alone custom registry, and click Configure.

After the properties are set in this panel, click Apply. Under Additional Properties, click Custom properties to include additional properties that the custom user registry requires.

Note: Custom properties might include information such as specifying lists of users or groups.

When security is enabled and any of these custom user registry settings change, go to the Global security panel and click Apply to validate the changes.

WebSphere® Application Server Version 7.0 distinguishes between the user identities for administrators who manage the environment and server identities for authenticating server to server communications. In most cases, server identities are automatically generated and are not stored in a repository.

[AIX Solaris HP-UX Linux Windows] However, if you are adding a previous version node to the latest version cell and the previous version node used a server identity and password, you must ensure that the server identity and password for the previous version are defined in the repository for this cell. Enter the server user identity and password on this panel.

Primary administrative user name

Specifies the name of a user with administrative privileges that is defined in your custom user registry.

The user name is used to log on to the administrative console when administrative security is enabled. Version 6.1 requires an administrative user that is distinct from the server user identity so that administrative actions can be audited.

Attention: In WebSphere Application Server, Version 6.0.x, a single user identity is required for both administrative access and internal process communication. When migrating to Version 6.1 and later, this identity is used as the server user identity. You need to specify another user for the administrative user identity.

Automatically generated server identity

Enables the application server to generate the server identity, which is recommended for environments that contain only Version 6.1 or later nodes. Automatically generated server identities are not stored in a user repository.

Information	Value
Default:	Enabled

Server identity that is stored in the repository

Specifies a user identity in the repository that is used for internal process communication. Cells that contain Version 6.1 or later nodes require a server user identity that is defined in the active user repository.

Information	Value
Default:	Enabled

Server user ID or administrative user on a Version 6.0.x node

Specifies the user ID that is used to run the application server for security purposes.

Password

Specifies the password that corresponds to the server ID.

Custom registry class name

Specifies a dot-separated class name that implements the com.ibm.websphere.security.UserRegistry interface.

Put the custom registry class name in the class path. A suggested location is the following directory.

%install_root%/lib/ext

Information	Value
Data type:	String
Default:	com.ibm.websphere.security.FileRegistrySample

Ignore case for authorization

Indicates that a case-insensitive authorization check is performed when you use the default authorization.

Information	Value
Default:	Disabled
Range:	Enabled or Disabled