Global security and server security
The term global security refers to the security configuration that is effective for the entire security domain. A security domain consists of all the servers configured with the same user registry realm name.
The realm can be the machine name of an LDAP user registry. Since LDAP is distributed, this allows for a multiple node configuration in a Network Deployment environment. The basic requirement for a security domain is that the access ID returned by the registry from one server within the security domain is the same access ID that is returned from the registry on any other server within the same security domain. The access ID is the unique identification of a user and is used during authorization to determine if access is permitted to the resource.
For z/OS, when a local OS registry is chosen, the realm name is the daemon IP name registered for the sysplex. In some cases, the realm can be the machine name of a Local OS user registry. In this case, all appservers must reside on the same physical machine.
Global security configuration includes...
- Common user registry
- authentication mechanism
- Java 2 Security Manager
- JAAS
- Java 2 Connector authentication data entries
- CSIv2/SAS authentication protocol
By default, the global security configuration applies to every server within the security domain. You can override portions of the configuration at the server level. The attributes that are configurable at a server level include security enablement for the server, Java 2 Security Manager enablement, and CSIv2/SAS authentication protocol. You can disable security on individual appservers while global security is enabled, however, you cannot enable security on an individual application server while global security is disabled.
While appserver security is disabled for user requests, administrative and naming security is still enabled for that application server so that the administrative and naming infrastructure remains secure. If cell security is enabled, but security for individual servers is disabled, J2EE applications are not authenticated or authorized. However, naming and administrative security is still enforced. Consequently, because Naming Services can be called from user applications you need to grant Everyone access to the naming functions that are required so that these functions accept unauthenticated requests. User code does not directly access administrative security except through the supported scripting tools.