Job manager security
When performing a job manager registration process there are a number of WAS security impacts to consider.
New feature: In WAS ND v7.0 flexible management has been 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 appservers registered to administrative agents and dmgr servers known to the job manager through a registration process. After you register the servers, we can queue admin jobs directed at the appservers or dmgrs through the job manager. We can submit these jobs to a large number of servers over a geographically dispersed area.
- Security configuration requirements should be kept to a minimum prior to registration.
- Allow an agent or a dmgr to be federated to the job manager with almost any security configuration. Some exceptions include:
- Leverage the creation of a chained certificate to exchange only the long-lived root certificates between an administrative agent, dmgr and job manager.
When a personal certificate expires in either the administrative agent, dmgr or the job manager, it does not affect trust that was established during federation.
- Use the Rivest Shamir Adleman (RSA) certificate administrative-specific authentication mechanism, which does not rely on shared keys and is the default admin authentication mechanism for the job manager.
The RSA token authentication mechanism is also new to this release of WAS.
- Add a profile Universal Unique Identifier (UUID) to all certificates generated in WAS V7.0.
This profile UUID is used to authorize requests to extract jobs from the job manager queue.
- Job Manager jobs can be associated with caller credentials; either LTPA or Kerberos, or with specified credentials using a user ID and password).
Both are stored with the job. The password is obfuscated using the standard utilities and can be encrypted when the password encryption plug point is enabled. LTPA and Kerberos are refreshed as long as the authentication mechanism allows them to be refreshed.
- Administrative agent or dmgr access to FileTransferServlet is performed by sending a valid RSA certificate that is trusted by the job manager and is validated by CertPath.
The required admin roles for executing flexible management jobs are defined by the underlying admin 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 admin roles are:
- View data requires the monitor role.
- Update data requires the configurator role.
- Manage jobs requires the operator role.
- Register or un-register managed nodes requires the administrator role.
Related conceptsRSA token authentication mechanism
Lightweight Third Party Authentication
Kerberos (KRB5) authentication mechanism support for security
Job manager settings
Set the RSA token authentication mechanism
Set admin authentication
Administer nodes using the job manager
Set job managers
Job status collection