Setting Up Control-M Access and Authorizations

This procedure describes how to set up access to Helix Control-M to register the Control-M/Agents, which is done by the Control-M Administrator.

Begin

1. Generate an Agent token associated with an Agent tag. For more information, see Agent Token Management.
2. Define a role or create a new role that is responsible to connect between the Control-M/Agent in the Kubernetes cluster and the Helix Control-M/Server. For more information, see User and Role Authorizations. 
3. In this role, grant authorizations to the Agents with the relevant tag with an access level of UPDATE or FULL (through Configuration > Agents, Agentless Hosts, and Host Groups). 

1. If you plan to dynamically deploy additional plug-ins (as described in Setting-Up-Dynamic-Deployment-of-Additional-Plug-ins), grant the following additional authorizations:
   • Select Tools > Application Integrator and grant an access level of BROWSE or higher. 
   • Select Configuration > Plug-ins, set the relevant tag, and grant an access level of BROWSE or higher.
2. Generate an API token using the same role as in the previous steps.
   This API token authenticates the connection to the Automation API server. For more information, see Creating an API Token.