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:
  1. Click Security > Global security.
  2. 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.

Avoid trouble Avoid trouble: Any settings that are related to the System Authorization Facility (SAF) might not be visible on this panel. To modify these settings:
  1. Go to the panel for SAF by clicking Security > Global security > External authorization providers.
  2. Select System Authorization Facility (SAF) from the drop-down list under the Authorization provider option.
  3. Click Configure.
gotcha

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 onto 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, 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.

Default: Enabled

User identity for the z/OS started task

Specifies the user identity that is associated with the z/OS system started task. Each controller and server can have its own identity.

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.

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.

Default: Disabled
Range: Enabled or Disabled



Related tasks
Configuring stand-alone custom registries
Related reference
Servlet security methods
Stand-alone custom registry wizard settings
Reference topic Reference topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 3:08:41 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=usec_customreg
File name: usec_customreg.html