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.

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:

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:

 

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.

 

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:





 

Related tasks


Select a registry or repository