Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users


Job manager security

When performing a job manager registration process there are a number of WAS security impacts to consider.

In WAS v7.0, a new style of system management called flexible management was introduced. It differs from the existing style of synchronous invocation and response calls through wsadmin or Java APIs by offering an asynchronous job queuing mechanism for administration purposes. At the core of flexible management is a new administrative process called the job manager. We can make both application servers registered to admin agents and dmgr servers known to the job manager through a registration process. After you register the servers, you can queue administrative jobs directed at the application servers or dmgrs through the job manager. We can submit these jobs to a large number of servers over a geographically dispersed area. There are a number of security considerations keep in mind both during and after the job manager registration process.

Consider the following:

The required administrative roles for executing flexible management jobs are defined by the underlying administrative commands used by those jobs. For example, the required role for starting and stopping servers is the operator role. The operator role is also required for execution of the flexible management jobs that start and stop servers. The general rules for assigning required administrative roles are:


RSA token authentication mechanism
Lightweight Third Party Authentication
Kerberos (KRB5) authentication mechanism support for security
Job manager
Job manager settings
Configure the RSA token authentication mechanism
Configure administrative authentication
Administer nodes remotely using the job manager
Configure job managers


Related


Administrative roles
Job status collection

+

Search Tips   |   Advanced Search