IBM WebSphere V5.0 Security - CGISecurity

From a security point of view, each application server process may be configuredto have a local or a remote Security Server. This notion of local or remote isrelative to the application server process. Deployment Managers and NodeAgent processes always have a Security Server and are used to performauthentication for the Deployment Manager, Node Agent, and for thoseapplication servers that were configured to use a remote Security Server.On some operating systems, like Unix for example, running the security serverwill require the highest user priority. This is because access to the operatingsystem functions to perform authentication based on local operating system userregistry requires root privilege.Many customers will not want to run application server processes with the rootprivilege because this implies that all application components (like servlets) willhave this privilege. In such cases, you have to consider how to configure securityand when to place the security server before deploying an application.9.1.3 Java Management Extension Architecture (JMX)Java Management Extension is a set of new interfaces and Java Beans thatallows you to perform configuration and management of WebSphere ApplicationServer components from custom applications without using the AdministrativeConsole or the wsadmin program.JMX uses Tivoli implementation scheme and provides client interface andscripting facility that allows the use of MBeans to manage WebSphereApplication Server. It is used for overall WebSphere system management tasks.Distributed administrative processes that run on each node have separateadministrative repository. The deployment manager that controls a group ofnodes provides the scope of visibility of the administrative processes in the cell.This is done through node managers as described in the section above. Next is aconceptual diagram of how JMX MBeans are used to perform differentadministrative tasks.220 IBM WebSphere V5.0 Security Handbook