Configuring multiperson authorization
You can navigate to the in any of the following ways:
Navigate to .
On the Home page, select . In the pop-up, select .
The following table lists the operations that can be performed on an access control policy.
Table:
Operations | Procedure |
|---|---|
Enable access control policy | |
Edit access control policy | |
Disable access control policy | |
Create multiperson authorization policy | |
Exempt an Active Directory user | Exempting an Active Directory user from multiperson authorization |
Delete custom policy | |
View multiperson authorization requests | |
Manage multiperson authorization requests |
To enable access control policy
- Navigate to Multiperson authorization.
- Click Enable.
- Confirm the change.
The access control policy is enabled.
You can edit and disable access control policies.
To edit an access control policy
- Navigate to Multiperson authorization.
- Click Edit.
- You can update any of the following fields:
Send requests to: Specify a comma-separated list of email addresses for notifications.
Expire pending requests after: Set the period (in hours) after which any pending requests will expire.
Delete resolved requests after: Specify the period (in days) after which resolved requests will be deleted.
- Click Save.
A request is created. Once it is approved, the access control policy is updated with the changes.
To disable access control policy
- Navigate to Multiperson authorization.
- Click Disable.
- Provide a reason in the pop-up and click Disable.
A request is created. Once it is approved, the access control policy is disabled.
The widget appears on the Homepage when there are one or more pending authorization requests that require user attention. The widget provides a quick snapshot of requests you have submitted as well as requests awaiting your review.
Note:
The counts displayed in the section on the dashboard and in reflect only active requests. They exclude requests in Done, Rejected, Expired, or Canceled states.
Viewing multiperson authorization requests
- On the Home page, select View requests in the Multiperson authorization widget.
- The Request management page lists all your requests for operations that require multiperson authorization. You can apply filters to view requests that you have submitted, requests sent to you for approval, and to narrow results by time frame or request status.
- Select the request ID to see the request details. The Audit trail tab gives more details on the status of your request.
- Select the Preview request details tab to see the changes that have been made as part of the request.
The requester can cancel his request by selecting Cancel request.
Users with the approver role can approve or reject the multiperson authorization requests.
To manage multiperson authorization requests
- On the Home page, select My actions in the Multiperson authorization widget.
You can also click on the User icon on the top right corner. In the pop-up, select the View authorization request option.
- The Request management page lists all the requests for operations that require multiperson authorization. You can apply filters to view requests that you have submitted, requests sent to you for approval, and to narrow results by time frame or request status.
- Select the request ID to see the request details. The Audit trail tab gives more details on the request. The Preview request details tab to see the changes that have been made as part of the request.
- Select Approve if you want to approve the request. In the Approve request pop-up, provide the reason for approving the request. Click Approve to complete the approval.
Select Reject if you want to reject the request. In the Reject request pop-up, provide the reason for rejecting the request. Click Reject to complete the rejection.
The reason field can contain 8 - 256 characters and may include only alphanumeric characters, spaces, periods, commas, underscores, and dashes.
- The Request details page gets updated with the details.
To create a multiperson authorization policy
- Navigate to Multiperson authorization.
- In the Custom policies panel, click Create.
- In the Create multiperson authorization policy window, enter the following details:
Policy name: Specify the policy name.
Expire pending requests after: Set the period (in hours) after which any pending requests will expire.
Send requests to: Specify a comma-separated list of email addresses for notifications.
Exempted accounts: Specify accounts that are exempted from multiperson authorization (if any).
To exempt an Active Directory (AD) user, enter the user name in the format
DOMAIN\username, for exampleFLEXAD\user. The user must be imported with the same domain-qualified user name. If the remote user domain is connected to a global catalog server, you can exempt AD users from any domain in the forest. If it is not, you can exempt only users from the configured domain.For more information, see Exempting an Active Directory user from multiperson authorization
Delete resolved requests after: Specify the period (in days) after which resolved requests will be deleted.
Approver role: Specify the approvers.
Number of approvals: Specify the number of approvals required.
Under Operations, select the operations that require multiperson authorization.
Under Behavior after approval, choose any option:
Automatically: The requested operation will be completed automatically after approval.
Manually: The requested operation will have to be completed manually after approval. Navigate to the Request management page. Select the request and click Complete operation.
- Click Create.
- In the confirmation pop-up, review the information and click Create.
After the quorum is reached, the request is scheduled by the Flex Appliance and marked as Done after execution.
The new policy details appears on the page.
You can also edit an existing multiperson authorization policy. Click the policy name to open the Edit window. Make the required changes and save the changes.
An Active Directory (AD) user is exempted from multiperson authorization in the Flex Appliance Console and in API operations only when the user is imported with a domain-qualified user name, and the same user name is added to the list of the policy.
To exempt an Active Directory user
- Determine the short domain name. It is the first value of the Base DN of the remote user domain. For example, if the Base DN is dc=flexad,dc=local, the short domain name is
FLEXAD. - Import the user with the short domain name prefix, for example
FLEXAD\user.See Importing a remote user or user group to the Flex Appliance Console.
- Add the same user name,
FLEXAD\user, to the Exempted accounts list of the multiperson authorization policy.For more information, see Creating multiperson authorization policy
You can update an existing user who must be exempted. Use the following procedure only if the AD user must be exempted and is currently imported without the domain prefix, for example user. Do not remove or re-import AD users who do not need to be exempted.
To update an existing user who must be exempted
- Record the roles and the account settings of the user.
- Revoke the personal API token of the user, and stop any automation that uses the token.
- On the Access management page, remove the imported user account, for example user.
Caution:
Remove only the imported account. Do not delete the user from Active Directory, and do not remove the remote user domain.
See Removing user or service accounts from the Flex Appliance Console.
- Import the user again with the domain-qualified user name, for example
FLEXAD\user. - Assign the roles that you recorded in step 1, and reconfigure the account settings.
- Add
FLEXAD\userto the Exempted accounts list of the policy. - Generate a new personal API token, and use it for all API operations.
To delete a custom policy
- Navigate to Settings > Security and compliance > Multiperson authorization.
- The Multiperson authorization page lists all the custom policies.
- You can delete the custom policy by clicking Delete on the right side of the row.
- Provide confirmation in the pop-up.
A request is created. Once it is approved, the access control policy is deleted.