Configure local operating system user registries

For security purposes, the WAS provides and supports the implementation for Windows NT systems and Windows 2000 operating system registries, AIX, Solaris and multiple versions of Linux operating systems. The respective operating system APIs are called by the product processes (servers) for authenticating a user and other security-related tasks (for example, getting user or group information). Access to these APIs are restricted to users who have special privileges. These privileges depend on the operating system and are described below.

Before configuring the LocalOS registry you need to know the user name (ID) and password to use here. This user can be any valid user in the registry. This user is referred to as either a product security server ID, a server ID or a server user ID in the documentation. Having a server ID means that a user has special privileges when calling protected internal methods. Normally, this ID and password are used to log into the administrative console after security is turned on. You can use other users to log in if those users are part of the administrative roles. When security is enabled in the product, this server ID and password are authenticated with the registry during product startup. If authentication fails, the server does not come up. So it is important to choose an ID and password that do not expire or change often. If the product server user ID or password need to change in the registry, ensure that the changes are performed when all the product servers are up and running. After the changes are completed in the registry, use the following steps to change the ID and the password information. Save, stop, and restart all the servers so that the product can use the new ID or password. If any problem arises after starting the product because of authentication problems (that cannot be fixed), disable security before the server can start up. To avoid this step, make sure that the changes are validated in the Global Security panel. After the server is up, change the ID and password information and enable security.

When using the Windows operating system, consider the following issues...

When using the UNIX operating systems (AIX and Solaris) and Linux, consider the following points...

The following steps are needed to perform this task initially when setting up security for the first time.

  1. Click Security > User Registries > LocalOS in the left navigation panel of the administrative console.

  2. Enter a valid user name in the Server User ID field.

  3. Enter the user password in the Server User Password field.

  4. Click OK. Validation of the user and password does not happen in this panel. Validation is only done when you click OK or Apply in the Global Security panel. If you are enabling security for the first time, complete the other steps and go to the Global Security panel. Verify that LocalOS is the Active User Registry. If security was already enabled and you had changed either the user or the password information in this panel, make sure to go to the Global Security panel and click OK or Apply to validate your changes. If your changes are not validated, the server might not come up.

The Local OS registry has been configured.

  1. If you are enabling security, complete the remaining steps. As the final step, ensure that you validate the user and password by clicking OK or Apply in the Global Security panel. Save, stop, and start all the product servers.

  2. For any changes in this panel to be effective, you need to save, stop and start all the product servers (cell, nodes and all the appservers).

  3. If the server comes up without any problems the setup is correct.


See Also

Configuring global security
Custom user registries
Local operating system user registry settings