IBM WebSphere V5.0 Security - CGISecurity

►
►
►
►
►
Operating system security should be considered in order to protect sensitive
WebSphere configuration files and to authenticate users when operating
system user registry is used for authentication. This is extremely important in
a distributed WebSphere environment when potentially different operating
systems and different user registries might be involved. Keeping the users
(and their passwords) and groups in sync across many different machines
might 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 by
introducing fine grained access, easily configurable security policy, extensible
access control structure and security checks for all Java programs (including
applets).
Common Secure Interoperability protocol adds additional security features
that enable interoperable authentication, delegation and privileges in CORBA
environment. It supports interoperability with EJB 2.0 specification and can be
used with SSL.
J2EE security uses the security collaborator to enforce J2EE-based security
policies and support J2EE security APIs. APIs are accessed from WebSphere
applications in order to access security mechanisms and implement security
policies.
WebSphere Application Server V5 security relies and enhances all the above
mentioned layers. It implements security policy for in unified manner for both
Web and EJB resources.
9.1.2 WebSphere security in a distributed environment
In a distributed environment, WebSphere Application Server may be installed in
the Network Deployment configuration, where WebSphere creates a network of
application servers instances supporting clustering, caching and the efficient
utilization of shared resources. Figure 9-2 presents a general architecture of the
WebSphere deployment configuration.
Chapter 9. WebSphere Application Server security 217