Standalone custom registry wizard settings


A wizard page exists in the admin console to aid in viewing the basic settings necessary to connect the application server to an existing standalone custom registry. After we have viewed the basic settings, we can also modify the existing standalone customer registry configuration using the admin console.

To view this security wizard page...

  1. Click Security > Global security > Security configuration wizard.

  2. Select the protection settings and click Next.

  3. Select the Standalone custom registry option and click Next.

We can modify the standalone custom registry configuration by completing the following steps:

  1. Click...

      Security | Global security

  2. Under User account repository, click the Available realm definitions drop-down list, select Standalone custom registry, and click Configure.

  3. 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 WAS 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.


      Table 1. Custom properties

      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 V4 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 the custom user registry.

The user name is used to log onto the admin console when administrative security is enabled. V6.1 requires an admin user that is distinct from the server user identity so that admin actions can be audited.

In WAS, Vs 5.x and 6.0.x, a single user identity is required for both admin access and internal process communication. When migrating to V6.1, this identity is used as the server user identity. specify another user for the admin user identity.

Custom registry class name

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





 

Related tasks


Set standalone custom registries

 

Related


Standalone custom registry settings
users.props file
groups.props file