Control-M/Agent security

Some of the jobs run by Control-M on a Control-M/Agent require job run as user authentications or SSH key definitions. The security method is determined by whether the job runs on an agent or if the job is executed from a remote host. SSH key authentication is only available for job run as users of remote host jobs using the SSH communication protocol.

The following job types require job Run as authentication settings:

• Jobs that run on remote host computers
• Jobs that run on agents on Windows computers in Log on as user mode
• Jobs that run on agents on UNIX run in non-root mode

The following procedures describe how to define, edit, and delete run as user authentication settings:

• Defining run as user authentication settings
• Editing run as user authentication settings
• Deleting run as user authentication settings

  NOTE: BMC recommends the following configurations:

• Run the Control-M/Agents in non-root mode (default).
• Run the Control-M/Agents in SSL/TLS configuration (non-default mode). Control M works with SSL and TLS protocols, which ensures secure communication between the various Control-M components. To configure SSL/TLS between Control-M/Server and Control-M/Agent, see Zone 2 and 3 SSL configuration.