+

Search Tips   |   Advanced Search

Configure stand-alone custom registries

Use the following information to configure stand-alone custom registries through the administrative console.

Before beginning this task, implement and build the UserRegistry interface. For more information on developing stand-alone custom registries refer to Developing stand-alone custom registries. The following steps are required to configure stand-alone custom registries through the administrative console.


Tasks

  1. Click Security > Global security.

  2. Under User account repositories, select Stand-alone custom registry and click Configure.

  3. Enter a valid user name in the Primary administrative user name field. This ID is the security server ID, which is only used for WAS security and is not associated with the system process that runs the server. The server calls the local operating system registry to authenticate and obtain privilege information about users by calling the native APIs in that particular registry.

  4. Enter the dot-separated class name that implements the com.ibm.websphere.security.UserRegistry interface in the Custom registry class name field. For the sample, this file name is com.ibm.websphere.security.FileRegistrySample.

    This file exists in all the product processes. Thus, this file exists in the cell class path and in all of the node class paths.

    The sample provided is intended to familiarize you with this feature. Do not use this sample in an actual production environment.

  5. Add our custom registry class name to the class path. (Dist) (ZOS) IBM recommends that we add the JAR file containing our custom user registry implementation to the following directory:

    • app_server_root/classes
    • (iSeries) profile_root/classes

      Important: The file can be located in any directory in the integrated file system. However, IBM recommends that the directory is not located in a product directory.

  6. Optional: Select the Ignore case for authorization option for the authorization to perform a case insensitive check. Enabling this option is necessary only when your user registry is case insensitive and does not provide a consistent case when queried for users and groups.

  7. Click Apply if we have any other additional properties to enter for the registry initialization.

  8. Optional: Enter additional properties to initialize your implementation.

    1. Click Custom properties > New.

    2. 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 chosen and reference their locations through custom properties. However, make sure that the directory has the appropriate access permissions.

      Property name Property value
      usersFile ${USER_INSTALL_ROOT}/customer_sample /users.props
      groupsFile ${USER_INSTALL_ROOT}/customer_sample /groups.props

      (iSeries) The QEJBSVR user profile must have Execute (*X) authority for the directory containing user.props and groups.propsfiles. Additionally, QEJBSVR must have Read and Execute (*RX) authority for the user.props and groups.propsfiles.

      Samples of these two properties are available in users.props file and groups.props file.

      (ZOS) To use the users.props and the groups.propsfiles on the z/OS platform, save these files in the ASCII format before calling them from the administrative console.

      The Description, Required, and Validation Expression fields are not used and can remain blank.

      In a WAS ND environment where multiple WAS processes exist, such as cell and multiple nodes in different machines, these properties are available for each process. Use the USER_INSTALL_ROOT relative name to locate any files, as this name expands to the product installation directory. If this name is not used, ensure that the files exist in the same location in all the nodes.

      WAS version 4-based custom user registry is migrated to the custom user registry based on the com.ibm.websphere.security.UserRegistry interface.

    3. Click Apply.

    4. Repeat this step to add other additional properties.

  9. Click Security > Global security.

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

  11. Select either the Automatically generated server identity or Server identity stored in the repository option. If we select the Server identity stored in the repository option, enter the following information:

    Server user ID or administrative user on a v6.0.x node

    Specify the short name of the account that is chosen in the second step.

    Server user password

    Password of the account that is chosen in the second step.

  12. Click OK and complete the required steps to turn on security.

This set of steps is required to set up the stand-alone custom registry and to enable security in WAS.

The security component of WAS expands a selected list of variables when enabling security. See the information about variable settings for more details.


What to do next

  1. Complete the remaining steps, if we are enabling security.

  2. Validate the user and password. Save and synchronize in the cell environment.

  3. After security is turned on, save, stop, and start all the product servers, including cell, nodes, and all of the application servers, for any changes to take effect. If the server comes up without any problems, the setup is correct.


Subtopics

  • Select a registry or repository
  • (iSeries) Create a classes subdirectory in your profile for custom classes
  • Developing stand-alone custom registries
  • WebSphere variables settings