The following information provides an overview of security in WebSphere® Application Server.
IBM WebSphere Application Server provides a unified, policy-based, and permission-based model for securing Web resources, Web service endpoints, and enterprise JavaBeans according to J2EE specifications. Specifically, WebSphere Application Server complies with J2EE specification Version 1.4 and has passed the J2EE Compatibility Test Suite.
The standard security models and interfaces that support secure socket communication, message encryption, and data encryption are the Java Secure Socket Extension (JSSE) and the Java Cryptographic Extension (JCE).
An application server plays an integral part in the multiple-tier enterprise computing framework. IBM WebSphere Application Server adopts the open architecture paradigm and provides many plug-in points to integrate with enterprise software components. Plug-in points are based on standard J2EE specifications wherever applicable.
The dark blue shaded background indicates the boundary between the WebSphere Application ServerVersion 7.0 and other business application components.
In WebSphere Application ServerVersion 7.0 for z/OS®, security services are configured at a cell level. The configurable services include a web authentication mechanism, a user registry, and an access control manager. Unless otherwise specified, the access control facility is provided by WebSphere bindings.
WebSphere Application Server for z/OS-specific security: WebSphere Application Server for z/OS provides the same functions that non-z/OS platforms provide with some additional optional features. In WebSphere Application Server for z/OS, security services are configured at a cell level. The configurable services include a Web authentication mechanism, a user registry, and an authorization facility. Authorization facility is provided by WebSphere bindings.
Unlike other platforms, WebSphere Application Server for z/OS offers security facilities (extensions) that require permission to protected resources and files because z/OS is secure by default. While it can be configured similarly to other WebSphere Application Server platforms, WebSphere Application ServerVersion 7.0 for z/OS provides support for configuring the active WebSphere Application Server user registry as LDAP or a Custom registry while also taking advantage of RACF® and SAF services such as the ones pointed out in System Authorization Facility security. For more information, refer to WebSphere Application Server configurations information in this article.
For more information on RACF profiles and RACF classes, refer to the z/OS Security Server RACF System Administrator's Guide.
ICH420I PROGRAM BBORSMCT FROM LIBRARY WAS.SBBOLD2 CAUSED THE ENVIRONMENT TO BECOME UNCONTROLLED. BPXP014I ENVIRONMENT MUST BE CONTROLLED FOR DAEMON (BPX.DAEMON) PROCESSING.
name --> errno value --> 157 --> 0x9d name --> errno2 value --> 151782063 --> 0x090C02AFThe 02AF indicates that the program controlled bit is not properly set. The specified function is not supported in an address space where a load is done that is not program controlled.
Although program control is enabled on the z/OS system, the program control extended control bits for the application server's native modules will not be enabled. To prevent or resolve this problem enable the program control bits for all of the native load modules in the SMP/E HTTP Server file system (HFS).
Identification management: To take advantage of SAF Security features , users must identify themselves using a z/OS-based user ID. You can use principal mapping modules to map a J2EE identity to your platform-based user ID (in this case a RACF user ID). A principal mapping must be created from the LDAP user ID to the RACF user ID in order for the SAF EJBROLE checks to be done. This means a mapping login module must be available to derive a z/OS user ID from the configured user in the LDAP registry. (SMF auditing (using SAF) can be used to track these changes.)
For more information, refer to Custom System Authorization Facility mapping modules and Installing and configuring a custom System Authorization Facility mapping module for WebSphere Application Server.
Information about users and groups reside in a user registry. In WebSphere Application Server, a user registry authenticates a user and retrieves information about users and groups to perform security-related functions, including authentication and authorization.
In addition to Local OS and LDAP registries, WebSphere Application Server also provides a plug-in to support any registry by using the Custom registry feature (also referred as Custom user registry).
When the Local OS registry implementation of WebSphere Application Server is chosen, it enables you to integrate the functionality of the z/OS Security Server, such as Resource Access Control Facility (RACF), using the Security Access Facility (SAF) in the WebSphere environment directly. If you configure your active LDAP or Custom user registry you can also take advantage of these z/OS Security Server facilities by configuring a custom or IBM-supplied pluggable mapping module (followed by a WebSphere Application Server for z/OS-supplied module) in the appropriate System Login configurations.
If a registry other than Local OS is selected and no mapping is done (or no valid mapping is available for a particular identity), these facilities are unavailable.
The LDAP UserRegistry supports the mapping function.
For more information, refer to Selecting a registry or repository.
WebSphere Application Server configurations: With WebSphere Application ServerVersion 7.0 for z/OS you can integrate existing non-z/OS applications with z/OS-specific facilities such as System Authorization Facility (SAF) and RACF. This allows you to unify registries for WebSphere Application Server for z/OS and non-z/OS platforms. For example:
Application server configuration | Registry type | Authorization method | Advantage |
---|---|---|---|
WebSphere Application Server | LDAP | WebSphere bindings and external security providers such as Tivoli® Access Manager | Shared registries (across a heterogeneous platform) |
WebSphere Application Server for z/OS | RACF | WebSphere bindings and RACF EJBROLEs | Centralized access and auditing ability (can include servers running Version 4.0) |
WebSphere Application Server mixed environment | LDAP or Custom | WebSphere bindings, external security providers, and RACF EJBROLEs | Shared registries, centralized access, and auditing ability |
Lightweight Third Party Authentication generates a security token for authenticated users, which can be used to represent that authenticated user on subsequent calls to the same or other servers within a single sign-on (SSO) domain.
Security support for Kerberos as the authentication mechanism has been added for this release of WebSphere Application Server. Kerberos is a mature, flexible, open, and very secure network authentication protocol. Kerberos includes authentication, mutual authentication, message integrity and confidentiality and delegation features.
IIOP Authentication protocol refers to the mechanisms used to authenticate requests from a Java Client to a WebSphere Application Server for z/OS, or between J2EE Application Servers. Common Secure Interoperability Version 2 (CSIv2) is implemented in WebSphere Application Serverfor z/OS Version 6.x or later and is considered the strategic protocol.
WebSphere Application Server supports the J2EE Connector architecture and offers container-managed authentication. It provides a default J2C principal and credential mapping module that maps any authenticated user credential to a password credential for the specified Enterprise Information Systems (EIS) security domain. z/OS-specific connectors are also supported when the EIS system is in the same security domain as WebSphere Application Server. In this case, passwords are not required, because authenticated credentials used for J2EE requests can be used as EIS credentials.
WebSphere Application Server enables you to secure Web services based upon the Organization for the Advancement of Structured Information Standards (OASIS) Web services security Version 1.1 specification. These standards address how to provide protection for messages exchanged in a Web service environment. The specification defines the core facilities for protecting the integrity and confidentiality of a message and provides mechanisms for associating security-related claims with the message.
Security attribute propagation
allows communication from a WebSphere Application Server, WebSphere Application Server, Network Deployment, or WebSphere Application Server, Express LDAP user registry
to a WebSphere Application Server for z/OS SAF
user registry.
In WebSphere Application Server, the interoperability mode option enables Single Sign-on (SSO) connections between WebSphere Application Server version 5.1.1 or later to interoperate with previous versions of the application server. When you select this option, WebSphere Application Server adds the old-style LtpaToken into the response so that it can be sent to other servers that work only with this token type. This option applies only when the Web inbound security attribute propagation option is enabled. For more information on single sign-on, refer to Implementing single sign-on to minimize web user authentications
Each container provides two kinds of security: declarative security and programmatic security. In declarative security, the security structure of an application, including data integrity and confidentiality, authentication requirements, security roles, and access control, is expressed in a form external to the application. In particular the deployment descriptor is the primary vehicle for declarative security in the J2EE platform. WebSphere Application Server maintains a J2EE security policy, including information derived from the deployment descriptor and specified by deployers and administrators in a set of XML descriptor files. At run time, the container uses the security policy defined in the XML descriptor files to enforce data constraints and access control. When declarative security alone is not sufficient to express the security model of an application, the application code can use programmatic security to make access decisions. The application programming interface (API) for programmatic security consists of two methods of the Enterprise JavaBeans (EJB) EJBContext interface (isCallerInRole, getCallerPrincipal) and three methods of the servlet HttpServletrequest interface (isUserInRole, getUserPrincipal, getRemoteUser).
From a security perspective, every application server process consists of a Web container, an EJB container, and the administrative subsystem. There are many other components that constitute a server process, which are not discussed here. Remote interfaces to the administrative subsystem, including the Admin Service interface through Java Management Extensions (JMX) connectors, the user registry interface, and the naming interface are protected by extended security role-based access control. All the system code, including the administrative subsystem, the Web container, and the EJB container code, are running in the WebSphere Application Server security domain. The system code, shown in the WebSphere Application Server security domain box in the following diagram, is granted AllPermission and can access all system resources. Application code running in the application security domain, which by default is granted permissions according to J2EE specifications, only can access a restricted set of system resources. WebSphere Application ServerVersion 7.0 run-time classes are protected by WebSphere Application Server class loader and are kept invisible to application code.
In
declarative security, the security structure of an application, including
data integrity and confidentiality, authentication requirements, security
roles, and access control, is expressed in a form external to the
application. The deployment descriptor is the primary vehicle for
declarative security in the J2EE platform. WebSphere Application ServerVersion 7.0 maintains a J2EE
security policy, including information derived from the deployment
descriptor and specified by deployers and administrators in a set
of XML descriptor files. At run time, the container uses the security
policy defined in the XML descriptor files to enforce data constraints
and access control.
When declarative security
alone is not sufficient to express the security model of an application,
the application code can use programmatic security to make access
decisions. The API for programmatic security consists of two methods
of the EJB EJBContext interface (isCallerInRole, getCallerPrincipal)
and the three methods of the servlet HttpServletrequest interface
(isUserInRole, getUserPrincipal, getRemoteUser).
WebSphere Application Server supports the Java 2 security model. All the system codes in the yellow box, including the administrative subsystem, the Web container, and the EJB container code, are running in the WebSphere Application Server security domain, which in the present implementation are granted with AllPermission and can access all system resources. Application code running in the application security domain, which by default is granted with permissions according to J2EE specifications, can access only a restricted set of system resources. WebSphere Application Server run-time classes are protected by the WebSphere Application Server class loader and are kept invisible to application code.
WebSphere Application Server supports the J2EE Connector architecture and offers container-managed authentication. It provides a default J2C principal and credential mapping module that maps any authenticated user credential to a password credential for the specified Enterprise Information Systems (EIS) security domain.
All of the application server processes, by default, share a common security configuration, which is defined in a cell-level security XML document. The security configuration determines whether WebSphere Application Server security is enforced, whether Java 2 security is enforced, the authentication mechanism and user registry configuration, security protocol configurations, JAAS login configurations, and Secure Sockets Layer configurations. Applications can have their own unique security requirements. Each application server process can create a per server security configuration to address its own security requirement. Not all security configurations can be modified at the application server level. Some security configurations that can be modified at application server level include whether application security should be enforced, whether Java 2 security should be enforced, and security protocol configurations.
For more
general information refer to Security states with thread identity support.
The administrative subsystem security configuration is always determined by the cell level security document. The Web container and EJB container security configuration are determined by the optional per server level security document, which has precedence over the cell-level security document.
Security configuration, both at the cell level and at the application server level, are managed either by the Web-based administrative console application or by the appropriate scripting application.
On WebSphere Application Server, Express, the local
OS user registry does not support the mapping function.
When the
LTPA authentication mechanism is configured and single sign-on (SSO)
is enabled, an authenticated client is issued a security cookie, which
can represent the user within the specified security domain.
It is recommended that you use Secure Sockets Layer (SSL) to protect the security cookie or Basic Authentication information from being intercepted and replayed. When a trust association is configured, WebSphere Application Server can map an authenticated user identity to security credentials based on the trust relationship established with the secure reverse proxy server.
When security is enabled, the EJB container enforces access control on EJB method invocation. The authentication takes place regardless of whether a method permission is defined for the specific EJB method.
A Java application client can provide the authentication
data in several ways. Using the sas.client.props file, a Java client can specify whether to use a user
ID and password to authenticate or to use an SSL client certificate
to authenticate. The client certificate is stored in the key file
or in the hardware cryptographic card, as defined in a sas.client.props file.
The user ID and password can be optionally defined in the sas.client.props file.
At run time, the Java client
can either perform a programmatic login or perform a lazy authentication.
In lazy authentication when the Java client is accessing a protected enterprise
bean for the first time, the security run time tries to obtain the
required authentication data. Depending on the configuration setting
in sas.client.props file the security runtime either looks
up the authentication data from this file or prompts the user. Alternatively,
a Java client can use programmatic login. WebSphere Application Server supports the JAAS
programming model and the JAAS login (LoginContext) is the recommended
way of programmatic login. The login_helper request_login helper
function is deprecated in Version 6.x and Version 7.0. Java clients
programmed to the login_helper APT can run in this version.
The EJB security
collaborator enforces role-based access control by using an access
manager implementation.
An access manager makes authorization decisions based on the security policy derived from the deployment descriptor. An authenticated user principal can access the requested EJB method if it has one of the required security roles. EJB code can use the EJBContext methods isCallerInRole and getCallerPrincipal. EJB code also can use the JAAS programming model to perform JAAS login and WSSubject doAs and doAsPrivileged methods. The code in the doAs and doAsPrivileged PrivilegedAction block executes under the Subject identity. Otherwise, the EJB method executes under either the RunAs identity or the caller identity, depending on the RunAs configuration. The J2EE RunAs specification is at the enterprise bean level. When RunAs identity is specified, it applies to all bean methods. The method level IBM RunAs extension introduced in Version 4.0 is still supported in this version.
Federal Information Processing Standards (FIPS) are standards and guidelines issued by the National Institute of Standards and Technology (NIST) for federal computer systems. FIPS are developed when there are compelling federal government requirements for standards, such as for security and interoperability, but acceptable industry standards or solutions do not exist.
WebSphere Application Server integrates cryptographic
modules including Java Secure Socket Extension (JSSE)
and Java Cryptography Extension (JCE), which have
undergone FIPS 140-2 certification.
For more
information, refer to Configuring Federal Information Processing Standard Java Secure Socket Extension files.
The IBMJCEFIPS cryptographic module contains the algorithms that are approved by FIPS, which form a proper subset of those in the IBM JCE modules.