In Control-M you can create users and roles, which enable you to limit the entities that a user is authorized to view or change. Users are granted permissions based on their associated role.
If Role A has authorizations to Folder
A container of jobs and sub-folders that passes its definitions to the included jobs and sub-folders A and Calendar A, then all associated users that are assigned Role A have access to those entities.
There are three predefined roles that are included in Control-M.
-
Administrator: Enables full access to all functionality.
-
Team Leader: Enables partial access with the ability to manage permissions for each member of the team.
-
Viewer: Enables view access.
To configure authentication for all Control-M users, BMC recommends that you perform these procedures in the following order:
You can create internal users in Control-M. However, BMC recommends that you configure a connection to an Identity Provider (IdP). This enables you to authenticate multiple external users with one configuration instead of creating individual internal users in Control-M. To connect Control-M to an IdP, see Configuring Authentication with an IdP. After an IdP is enabled, all users are authenticated via SAML 2.0.
If the IdP is down, users that are assigned to Admin roles can still log in using an Emergency URL, which enables Emergency users to access Control-M. An Emergency user is any internal user that is associated with the Admin role. BMC recommends that you copy the Emergency URL and save or bookmark it. If the IdP becomes unavailable, you will need the URL to log in to Control-M. To edit the list of existing Emergency users, you must disable the IdP configuration, as described in Updating Emergency Users. After it is disabled, users that are authenticated with the IdP cannot log in to Control-M. After you have updated the list of users and the IdP becomes available, re-enable IdP.
Before you delete a role, identify the Agent tagA logical name that is used to label specific Agents into a group with a specific authorization level(s) that is associated with the role. After you delete the role, you need to delete any Agent tokensAn authorization entity, required during Agent installation, that enables you to connect the Agent to your SaaS backend that are associated with the Agent tag(s) that you identified.
Adding a Role
This procedure describes how to create a role, which limits the associated user to specific authorizations and access levels.
Begin
-
From the Configuration domain, click
and then select Roles.The Roles tab appears.
-
Click Add Role.
The Add Role pane appears.
- In the General tab, do the following:
In the Role Name field, type a logical name for the role.
In the Description field, type a description for the role.
If you want this role to have access to Automation API
A set of programmatic interfaces that provide developers and DevOps engineers access to the capabilities of Control-M SaaS within the modern application release process, select the Automation API access checkbox.Do one of the following:
If you want to associate users in a specific organizational group in IdP, select Organizational Groups Only, and from the Set Organizational Groups drop-down list, select or search for the organizational groups from your IdP that you want to associate to this role.
If the list is empty, you need to manually add the names of the IdP groups by typing the name of the group and then click Add. The IdP group names are case sensitive and must appear exactly as they are in the IdP .
If you want to explicitly associate a specific IdP user directly in Control-M, regardless of the organizational group, select Organizational Users Only and from the Set Organizational Users drop-down list, search for the organizational user from your IdP or LDAP that you want to associate to this role.
If the list is empty, you need to manually add the names of the IdP or LDAP user by typing the name of the user and then click Add. The IdP and LDAP user names are case sensitive and must appear exactly as they are in the IdP or LDAP.
-
In the Access control tab, toggle on one or more of the following that you want to apply specific authorizations to this role, as described in Role Authorizations.
- Click Add.
Adding an Internal User
This procedure describes how to add a user in Control-M. User authorizations are determined by the roles that are associated to the user.
Begin
-
From the Configuration domain, click
and then select Users.The Users tab appears.
-
In the Email field, type the email address of the new user.
A confirmation email is sent to the new user that contains a link and a temporary password for first time use. The password expires in 7 days. If the password expires, you must delete the existing user and recreate the user.
-
In the Assigned roles drop-list, select one or more of the existing roles to assign to this user.
The role determines which authorizations the user has access to for all Control-M entities. To create a role, see Adding a Role.
-
Click Add.
The new user appears in the Users list.
Updating Emergency Users
This procedure describes how to update Emergency users in the event that IdP becomes unavailable (breaking glass procedure). This enables you and other Emergency users to continue working in Control-M. You can update the list of Emergency users to enable or disable specific users access to Control-M.
Begin
-
From the Configuration domain, click
and then select System Settings.The System Settings tab appears.
-
From the Identity Provider (IdP) drop-down, toggle off Enable SAML 2.0.
-
Click Save.
You are now working in Emergency mode and all users authenticated via IdP cannot log in to Control-M. Emergency users can log in with the following URL:
Emergency URL: <tenant_name>-emergency
-
To add an Emergency user, assign the Admin role to the user, as described in Adding an Internal User.
- Send the Emergency URL to all Emergency users.
- After IdP becomes available, toggle on Enable SAML 2.0.
Role Authorizations
The following table describes authorizations that you can apply to a role. All associated users to this role inherit the selected authorizations.
| Authorization | Description |
|---|---|
| Planning | Determines whether to allow access to specific folders, Run as usersAn OS account name that is used to execute the job on the host, and named pool variablesA type of variable with a pool parameter, that you set in one job and can reference in any subsequent job with the same pool parameter. A Named Pool is a logical grouping of variables.. |
| Folders |
Grants access to specific folders with an authorization level for each folder, as follows:
This authorization also determines whether associated users are granted access to the Folder Management tool. |
| Run as |
Enables associated users to use the listed run as users or pattern in job definitions
|
| Monitoring | Determines whether to allow access to specific jobs and servicesA set of workflows that serves a business purpose, and can be monitored as a single unit. |
| Job permissions |
Determines which of the following entities associated users can view on all jobs or on specific jobs with a filter:
Determines which of the following actions associated users can perform on all jobs or on specific jobs with a filter:
To add a filter, which includes or excludes jobs, click Add a filter and then apply the required If statement. If you want to add another group of fields which, when met, can include more fields, even if the other group of fields do not meet the conditions, click Add Condition and then select Add And Condition or Add Or Condition. |
| Service permissions |
Grants associated users or groups of users access to view services, perform job actions, run, hold, and release services, as follows:
|
|
Archived Viewpoints |
Grants associated users access to Archived Viewpoints, as follows:
|
| Tools | Determines whether to allow access to Application IntegratorA Control-M component that enables you to create an integration with a third-party business application, and then create custom job types that perform specialized tasks on your application, CalendarsA reusable job schedule that you can apply to many jobs, which enables you to perform schedule changes from a single location, EventsAn entity that creates a sequence relationship between jobs by enabling the successor job to execute after the predecessor job has executed, Resource PoolsA type of quantifiable resource, which represents the total amount of resources from a physical or logical device that a job can access, Lock ResourcesA type of resource that controls the flow of the workflow, which represents a physical or logical device that a folder, sub-folder, or job can access exclusively or share, Site StandardsA set of rules that are relevant to your organization and applied on the folder level, and that determines how users must define folders and jobs, and User ViewsA customization of the Control-M interface, which enables users to view specific functionality only. |
| Application Integrator |
Grants associated users access to Application Integrator, as follows:
|
| Calendars |
Grants access to specific calendars with an authorization level for each calendar, as follows:
|
| Events |
Grants access to specific events with an authorization level for each event, as follows:
|
| Lock Resources |
Grants access to specific Lock Resources with an authorization level for each Lock Resource, as follows:
|
| Pool Variables (API only) |
Grants associated users access to named pool variables using API commands, as follows:
|
|
Reports |
Grants access to Reports, as follows:
|
| Resource Pools |
Grants access to specific Resource Pools with an authorization level for each Resource Pool, as follows:
|
|
Secrets |
Grants access to specific Automation API Config secrets in the JSON with an authorization level for each secret, as follows:
After you update the role, you must regenerate an API token to use the updated authorizations, as described in Creating an API Token. |
| Site Standards |
Grants access to specific Site Standards with an authorization level for each Site Standard, as follows:
|
| User Views |
Grants access to specific user views with an authorization level for each user view, as follows:
|
| Configuration |
Enables the Administrator to delegate control to users to carry out specific administrative tasks on Agents, plug-ins |
| Agents |
Grants access to specific Agents as follows:
|
| Plug-ins |
Grants access to specific plug-ins with an authorization level for each plug-in, as follows:
|
| Connection Profiles |
Grants access to specific connection profiles with an authorization level for each connection profile, as follows:
|
| Users and Roles |
Grants associated users access to users and roles, as follows:
To generate new API tokens |
| Run as Definition |
Grants associated users access to manage Run as User definitions, as follows:
|
|
Admin Management |
Grants associated users access to the following categories, as follows:
If the access levels defined in Configuration and Security are higher than those defined in Agents and Host Groups, Plug-ins, and, Connection Profiles, the definitions in Admin Management take precedence and vice versa. |
| Advanced Admin Authorizations |
Grants associated users full permissions to access Agents, connection profiles, plug-ins, Host Groups, System Settings, and API Token management. To enable access to API Token management, you must verify that the Automation API access checkbox is enabled in the General tab. If the Automation API access checkbox is enabled and this option is disabled, associated users can only view their own API Tokens. If both options are enabled, associated users can view and delete API tokens that were created by other users, as well. In addition, they can generate new tokens with a different role authorization. |
| Alerts |
Determines whether to allow access to alerts
|
YouTube
Twitter
Facebook
LinkedIn