Configuring Dual Control for the Perform Model Conversion task

Edit online

Dual Control is configured through the User Management task on the Hardware Management Console or Support Element. When configuring Dual Control, a user role must be created where a task and target mapping are present indicating which task is under Dual Control for which targets.

Before creating a Dual Control user role for Perform Model Conversion, please be aware of the following:

When Dual Control is assigned to a given user on the Perform Model Conversion task, all operations previously listed will be under Dual Control.
Dual Control will require two users to interact with Dual Control requests, the user who creates the request, and a separate user who approves or rejects the request.

To begin, open the User Management task and click on Roles and create a new role. The role may be configured however you would like, giving access to objects, tasks and groups is completely dependent on your needs and system configuration. The Dual Control section of the role is where a task and target mapping is created, indicating which tasks and which targets will be under Dual Control when the role is assigned to a user. When proceeding through the role creation, you will eventually find the Dual Control section in the role, which is shown below.

Figure 1. Add Dual Control Task and Target Mapping: Select Task

Selecting a task is the first step in creating a Dual Control task and target mapping. The task which is selected will have Dual Control enabled for all objects which are selected in the later steps when this role is present. To create a Dual Control role for the Perform Model Conversion task, select Perform Model Conversion and click Next on the inner window. You will then be prompted to select the type of target to add to the mapping. This can be a type of object, a specific object, or a group of objects. When combined with the task, the object or objects you select will form a task and target mapping for Dual Control. This allows you to have as much granularity as you would like when selecting which objects will be a part of the task and target mapping. An example of including and excluding objects could be adding a group of production CPCs into a Dual Control mapping, but excluding CPCs in a disaster recovery data center to not hinder recovery time in the event of a data center recovery action. The following images show the various options of object selection when creating a Dual Control task and target mapping.

Figure 2. Add Dual Control Task and Target Mapping: Objects by type

Figure 3. Add Dual Control Task and Target Mapping: Specific objects

Figure 4. Add Dual Control Task and Target Mapping: Objects by group

Lastly, you will be prompted to select what roles or credentials will be used as an approver of the task and target mapping. Bear in mind, Dual Control requires two users to successfully interact with any Dual Control requests that are created. The role creation in this example would be assigned to someone who would create a Dual Control request and submit it for approval. The individual approving the request is determined in this step, and is completely dependent on your needs and system configuration.

Figure 5. Add Dual Control Task and Target Mapping: Dual Control

Once, the role has been created, it may be assigned to a user. Though, in order to access the task and objects the mapping is created for, the user must have access to the task and objects specified in the mapping by a role that is assigned to the user. The task and target mapping does not automatically give the user permission to the task or target within the Dual Control mapping.