Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Stand-alone custom registry wizard settings
A wizard page exists in the administrative console to aid in viewing the basic settings necessary to connect the application server to an existing stand-alone custom registry. After we have viewed the basic settings, you can also modify the existing stand-alone customer registry configuration .
To view this security wizard page...
- Click Security > Global security > Security configuration wizard.
- Select your protection settings and click Next.
- Select the Stand-alone custom registry option and click Next.
We can modify your stand-alone custom registry configuration...
- Click Security > Global security.
- Under User account repository, click the Available realm definitions drop-down list, select Stand-alone custom registry, and click Configure.
- Enter additional properties to initialize your implementation
- Click Custom properties > New.
- Enter the property name and value. For the sample, enter the following two properties. It is assumed that the users.props file and the groups.props file are in the customer_sample directory under the product installation directory. We can place these properties in any directory that you choose and reference their locations through Custom properties. However, make sure that the directory has the appropriate access permissions.
Custom properties.
This table lists additional custom properties when changing stand-alone custom registry wizard settings.
Property name Property value usersFile ${USER_INSTALL_ROOT}/customer_sample /users.props groupsFile ${USER_INSTALL_ROOT}/customer_sample /groups.props Samples of these two properties are available in reference topics for the users.props file and the groups.props file. See the related links below for more information.
The Description, Required, and Validation Expression fields are not used and can remain blank.
WAS Version 4 based custom user registry is migrated to the custom user registry based on the com.ibm.websphere.security.UserRegistry interface.
- Click Apply.
Primary administrative user name
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. v6.1 requires an administrative user that is distinct from the server user identity so that administrative actions can be audited.
In WAS, v6.0.x, a single user identity is required for both administrative access and internal process communication. When migrating to v6.1, this identity is used as the server user identity. You need to specify another user for the administrative user 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.
- %install_root%/lib/ext
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
Configure stand-alone custom registries
Related
Stand-alone custom registry settings
users.props file
groups.props file