IBM WebSphere V5.0 Security - CGISecurity

►►►►►Operating system security should be considered in order to protect sensitiveWebSphere configuration files and to authenticate users when operatingsystem user registry is used for authentication. This is extremely important ina distributed WebSphere environment when potentially different operatingsystems and different user registries might be involved. Keeping the users(and their passwords) and groups in sync across many different machinesmight be a problematic administration task.Standard Java security is provided through the Java Virtual Machine (JVM)used by WebSphere and the Java security classes.Java 2 security enhances standard Java Virtual Machine security byintroducing fine grained access, easily configurable security policy, extensibleaccess control structure and security checks for all Java programs (includingapplets).Common Secure Interoperability protocol adds additional security featuresthat enable interoperable authentication, delegation and privileges in CORBAenvironment. It supports interoperability with EJB 2.0 specification and can beused with SSL.J2EE security uses the security collaborator to enforce J2EE-based securitypolicies and support J2EE security APIs. APIs are accessed from WebSphereapplications in order to access security mechanisms and implement securitypolicies.WebSphere Application Server V5 security relies and enhances all the abovementioned layers. It implements security policy for in unified manner for bothWeb and EJB resources.9.1.2 WebSphere security in a distributed environmentIn a distributed environment, WebSphere Application Server may be installed inthe Network Deployment configuration, where WebSphere creates a network ofapplication servers instances supporting clustering, caching and the efficientutilization of shared resources. Figure 9-2 presents a general architecture of theWebSphere deployment configuration.Chapter 9. WebSphere Application Server security 217