Local operating system registries

With the registry implementation for the local operating system, the WAS authentication mechanism can use the user accounts database of the local operating system.

LDAP is a centralized registry. Most local operating system registries are not centralized registries.

WAS provides implementations for the Windows local accounts registry and domain registry, as well as implementations for the Linux, Solaris, and AIX user accounts registries. Windows Active Directory is supported through the LDAP user registry implementation discussed later.

For an Active Directory (domain controller), the three group scopes are Domain Local Group, Global Group, and Universal Group. For an Active Directory (Domain Controller), the two group types are Security and Distribution. When a group is created, the default value is Global and the default type is Security. With Windows NT domain registry support for Windows 2000 and 2003 domain controllers, WAS only supports Global groups that are the Security type. IBM recommends that you use the Active Directory registry support rather than a Windows NT domain registry if we use Windows 2000 and 2003 domain controllers because the Active Directory supports all group scopes and types. The Active Directory also supports a nested group not support by Windows NT domain registry. The Active Directory is a centralized control registry.

WAS does not have to install the member of the domain because it can be installed on any machine on any platform. Note that the Windows NT domain native call returns the support group only without an error.

Do not use a local operating system registry in a WAS environment where appservers are dispersed across more than one machine because each machine has its own user registry.

The Windows domain registry and Network Information Services (NIS) are exceptions. Both the Windows domain registry and Network Information Services (NIS) are centralized registries. The Windows domain registry is supported by WAS; however, NIS is not supported.

As mentioned previously, the access IDs taken from the user registry are used during authorization checks. Because these IDs are typically unique identifiers, they vary from machine to machine, even if the exact users and passwords exist on each machine.

Web client certificate authentication is not currently supported when using the local operating system user registry. However, Java client certificate authentication does function with a local operating user registry. Java client certificate authentication maps the first attribute of the certificate domain name to the user ID in the user registry.

Even though Java client certificates function correctly, the following error displays in SystemOut.log:

CWSCJ0337E: The mapCertificate method is not supported The error is intended for Web client certificates; however, it also displays for Java client certificates. Ignore this error for Java client certificates.

 

Required privileges

The user that is running the WAS process requires enough operating system privilege to call the Windows systems API (API) for authenticating and obtaining user and group information from the Windows operating system. This user logs into the machine, or if running as a service, is the Log On As user. Depending on the machine and whether the machine is a standalone machine or a machine that is part of a domain or is the domain controller, the access requirements vary.

• For a standalone machine, the user:

  • Is a member of the admin group.

  • Has the Act as part of the operating system privilege.

  • Has the Log on as a service privilege, if the server is run as a service.

• For a machine that is a member of a domain, only a domain user can start the server process and:

  • Is a member of the domain admin groups in the domain controller.

  • Has the Act as part of the operating system privilege in the Domain security policy on the domain controller.

  • Has the Act as part of the operating system privilege in the Local security policy on the local machine.

  • Has the Log on as a service privilege on the local machine, if the server is run as a service.

    The user is a domain user and not a local user, which implies that when a machine is part of a domain, only a domain user can start the server.

• For a domain controller machine, the user:

  • Is a member of the domain admin groups in the domain controller.

  • Has the Act as part of the operating system privilege in the Domain security policy on the domain controller.

  • Has the Log on as a service privilege on the domain controller, if the server is run as a service.

If the user running the server does not have the required privilege, we might see one of the following exception messages in the log files:

• A required privilege is not held by the client.

• Access is denied.

Note on starting an appserver on the Microsoft® Windows Vistaoperating system or Microsoft® Windows Server 2008 operating system: On the Windows Vista operating system or Windows Server 2008, the appserver must be started with Administrator privileges if we are using a Command Prompt. Start the appserver from a Command Prompt window that is launched by performing the following actions:

• Right-click a Command Prompt shortcut.

• Click Run As Administrator.

  When you open the Command Prompt window as Administrator, an operating-system dialog appears that asks you to continue. Click Continue to proceed.

 

Domain and local user registries

When WAS is started, the security run-time initialization process dynamically attempts to determine if the local machine is a member of a Windows domain. If the machine is part of a domain then by default both the local registry users or groups and the domain registry users or groups can be used for authentication and authorization purposes with the domain registry taking precedence. The list of users and groups that is presented during the security role mapping includes users and groups from both the local user registry and the domain user registry. The users and groups can be distinguished by the associated host names.

WAS does not support trusted domains.

If the machine is not a member of a Windows system domain, the user registry local to that machine is used.

 

Use both the domain user registry and the local operating system registry

When the machine that hosts the WAS process is a member of a domain, both the local and the domain user registries are used by default.

The following section describes more on this topic and recommends some best practices to avoid unfavorable consequences.

Although this section does not directly describe z/OS considerations, you should be aware that overall security operations are affected by how well you set up these registries.

• Best practices

  In general, if the local and the domain registries do not contain common users or groups, it is simpler to administer and it eliminates unfavorable side effects. If possible, give users and groups access to unique security roles, including the server ID and admin roles. In this situation, select the users and groups from either the local user registry or the domain user registry to map to the roles.

  In cases where the same users or groups exist in both the local user registry and the domain user registry, IBM recommends that at least the server ID and the users and groups that are mapped to the admin roles be unique in the registries and exist only in the domain.

  If a common set of users exists, set a different password to make sure that the appropriate user is authenticated.

• How it works

  When a machine is part of a domain, the domain user registry takes precedence over the local user registry. For example, when a user logs into the system, the domain user registry tries to authenticate the user first. If authentication fails, the local user registry is used. When a user or a group is mapped to a role, the user and group information is first obtained from the domain user registry. In case of failure, the local user registry is tried. However, when a fully qualified user or a group name, one with an attached domain or host name, is mapped to a role, only that user registry is used to get the information. Use the admin console or scripts to get the fully qualified user and group names, which is the recommended way to map users and groups to roles.

  Tip: A user, Bob, on one machine in the local OS user registry, for example, is not the same as the user Bob on another machine in the domain user registry, for example, because the unique ID of Bob, which is the security identifier [SID] in this case, is different in different user registries.

• ExamplesThe MyMachine machine is part of the MyDomain domain. The MyMachine machine contains the following users and groups:

  • MyMachine\user2

  • MyMachine\user3

  • MyMachine\group2

  The MyDomain domain contains the following users and groups:

  • MyDomain\user1

  • MyDomain\user2

  • MyDomain\group1

  • MyDomain\group2

  Here are some scenarios that assume the previous set of users and groups:

  1. When user2 logs into the system, the domain user registry is used for authentication. If the authentication fails because the password is different, for example, the local user registry is used.

  2. If the MyMachine\user2 user is mapped to a role, only the user2 user in MyMachine machine has access. Thus, if the user2 password is the same on both the local and the domain user registries, the user2 user cannot access the resource because the user2 user is always authenticated using the domain user registry. If both user registries have common users, IBM recommends that we have different passwords.

  3. If the group2 group is mapped to a role, only the users who are members of the MyDomain\group2 group can access the resource because group2 information is first obtained from the domain user registry.

  4. If the MyMachine\group2 group is mapped to a role, only the users who are members of the MyMachine\group2 group can access the resource. A specific group is mapped to the role (MyMachine\group2 instead of just group2).

  5. Use either the user3 user or the MyMachine\user3 user to map to a role because the user3 user is unique as it exists in one user registry only.

  Authorizing with the domain user registry first can cause problems if a user exists in both the domain and local user registries with the same password. Role-based authorization can fail in this situation because the user is first authenticated within the domain user registry. This authentication produces a unique domain security ID used in WAS during the authorization check. However, the local user registry is used for role assignment. The domain security ID does not match the unique security ID that is associated with the role. To avoid this problem, map security roles to domain users instead of local users.

  Only a centralized repository can be used if more than one node is involved. This usage implies that only the domain user registry can be used because the user and group unique IDs (SIDs) differ on various nodes, as previously mentioned.

 

Use either the local or the domain user registry

. To access users and groups from either the local or the domain user registry, instead of both, set the com.ibm.websphere.registry.UseRegistry property. This property can be set to either local or domain. When this property is set to local (case insensitive) only the local user registry is used. When this property is set to domain, (case insensitive) only the domain user registry is used. Set this property by completing the following steps to access the Custom Properties panel in the admin console:

1. Click Security > Global security

2. Under User account repository, click the Available realm definitions drop-down list, select Local operating system, and click Configure.

3. Under Additional properties, click Custom properties.

We can also use wsadmin to configure this property. When the property is set, the privilege requirement for the user who is running WAS process does not change. For example, if this property is set to local, the user that is running the process requires the same privilege, as if the property was not set.

 

Use system user registries

The following notes apply when you use system user registries:

• [AIX] [HP-UX] [Linux] [Solaris]

  When using system user registries, the process ID that runs the WAS process needs the root authority to call the local operating system APIs for authentication and for obtaining user or group information.

• [AIX] [HP-UX] [Linux] [Solaris]

  Only the local machine user registry is used. Network Information Service (NIS) (Yellow Pages) is not supported.

• [HP-UX] If using the local operating system user registry, HP-UX must be configured in untrusted mode. Trusted mode is not supported if using the local operating system user registry.

• (Linux) [Solaris]

  For WAS local operating system registry to work on the Linux and Solaris platforms, a shadow password file must exist. The shadow password file is named shadow and is located in the /etc directory.

  If the shadow password file does not exist, an error occurs after enabling administrative security and configuring the registry as local operating system.

  To create the shadow file, run the pwconv command (with no parameters). This command creates an /etc/shadow file from the /etc/passwd file. After creating the shadow file, we can enable local operating system security successfully.

---

 

Related tasks

Select a registry or repository