Processing attestation mails
The Processes attestation mail approvals schedule starts the VI_Attestation_Process Approval Inbox process. This process runs the VI_MailApproval_ProcessInBox script, which searches the mailbox for new attestation mails and updates the attestation cases in the One Identity Manager database. The contents of the attestation mail are processed at the same time.
NOTE: The validity of the email certificate is checked with the VID_ValidateCertificate script. You can customize this script to suit your security requirements. Take into account that this script is also used for approval decisions for IT Shop requests by email.
If an self-signed root certification authority is used, the user account under which the One Identity Manager Service is running, must trust the root certificate.
TIP: The VI_MailApproval_ProcessInBox script finds the Exchange Web Service URL that uses AutoDiscover through the given mailbox as default. This assumes that the AutoDiscover service is running.
If this is not possible, enter the URL in the QER | Attestation | MailApproval | ExchangeURI configuration parameter.
Attestation mails are processed with the VI_MailApproval_ProcessMail script. The script finds the relevant approval decision, sets the Approved option if approval is granted, and stores the reason for the approval decision with the attestation cases. The attestor is found through the sender address. Then the attestation mail is removed from the mailbox depending on the selected cleanup method.
NOTE: If you use a custom mail template for the attestation mail, check the script and modify it as required. Take into account that this script is also used for approval decisions for IT Shop requests by email.
Default attestation and withdrawal of entitlements
One Identity Manager provide various default attestation procedures for different data situations and default attestation procedures.
Data situations for default attestations:
-
System entitlements owned by an employee
-
System entitlements assigned to system entitlements
-
System entitlements assigned to hierarchical roles
-
System roles assigned to an employee
-
Company resources assigned to system roles
-
System roles assigned to hierarchical roles
-
Business and application role memberships
-
Employee main data of a new One Identity Manager user
-
Employee main data of an existing One Identity Manager user
The attestation polices required for attesting employee main data are also supplied by default. You can also use the default supplied attestation policies without modifying them. The prerequisites and the attestation sequence for employee data are described in User attestation and recertification.
You can set up attestation policies easily in the Web Portal using default attestation procedures for other data situations. You can also use the default attestation policies supplied without customizing them. Furthermore, you can configure how to deal with denied attestations that are based on these default attestation procedures. If your specific data situation allows, denied entitlements can be removed by One Identity Manager following the attestation.
To remove denied permissions automatically
-
In the Designer, set the QER | Attestation | AutoRemovalScope configuration parameter and the configuration subparameters.
-
If the entitlements were obtained through IT Shop, specify whether these requests should be unsubscribed or canceled. To do this, set the QER | Attestation | AutoRemovalScope | PWOMethodName configuration parameter and select a value.
-
Abort: Requests are canceled. In this case, they do not go through a cancellation workflow. The requested entitlements are withdrawn without additional checks.
-
Unsubscribe: Requests are unsubscribed. They go through the cancellation workflow defined in the approval policies. Withdrawal of the entitlement can thus be subjected to an additional check.
If the cancellation is denied, the entitlement is not withdrawn even though the attestation has been denied.
If the configuration parameter is not set, the requests are canceled.
IMPORTANT: If role memberships or system roles are removed from an employee they lose the unapproved entitlement. They also lose all other company resources inherited through this role. These may be other system entitlements or account definitions. If necessary, system entitlements are removed and company resources are deleted from the employee.
Check whether your data situation allows automatic withdrawal of entitlements before you enable configuration parameters under QER | Attestation | AutoRemovalScope.
Automatic removal of entitlements is triggered by an additional approval step with the EX approval procedure in the default approval workflows.
Attestation sequence with subsequence withdrawal of denied entitlements:
-
Attestation is carried out using a default attestation procedure.
-
The attestor denies attestation. The approval step is not granted approval and approval is passed on the next approval level with the EX approval procedure.
-
The approval step triggers the AUTOREMOVE event. This runs the VI_Attestation_AttestationCase_AutoRemoveMembership process.
-
The process runs the VI_AttestationCase_RemoveMembership script. This removes the affected entitlement depending on which configuration parameters are set.
-
The script sets the approval step status to Denied. This means the entire attestation case is finally denied.
-
Tasks to recalculate inheritance are entered in the DBQueue.
Detailed information about this topic
Attesting system entitlements
| Installed modules: |
Target System Base Module |
When you use the System entitlement memberships attestation default attestation policy or have set up attestation policies with the System entitlement memberships attestation default attestation procedure, you can configure automatic removal of system entitlements through the QER | Attestation | AutoRemovalScope | GroupMembership configuration parameter. After attestation approval has been denied, One Identity Manager checks which type of assignment was used for the user account to become a member in the system entitlement.
Table 42: Effect of configuration parameters when attestation denied
|
QER | Attestation | AutoRemovalScope | GroupMembership | RemoveDirect |
Direct membership of the user account in the system entitlement, is removed. |
|
QER | Attestation | AutoRemovalScope | GroupMembership | RemovePrimaryRole |
If membership in the system entitlement was inherited through a primary role, the role is withdrawn from the employee.
This removes all indirect assignments obtained by the employee through this role. |
|
QER | Attestation | AutoRemovalScope | GroupMembership | RemoveRequestedRole |
If membership of the system entitlement was inherited through a requested role, the role request is canceled or unsubscribed.
This removes all indirect assignments obtained by the employee through this role.
Set the desired behavior in the QER | Attestation | AutoRemovalScope | PWOMethodName configuration parameter. For more information, see Default attestation and withdrawal of entitlements. |
|
QER | Attestation | AutoRemovalScope | GroupMembership | RemoveDelegatedRole |
If membership in the system entitlement was inherited through a delegated role, delegation of this role is canceled or unsubscribed.
This removes all indirect assignments obtained by the employee through this role.
Set the desired behavior in the QER | Attestation | AutoRemovalScope | PWOMethodName configuration parameter. For more information, see Default attestation and withdrawal of entitlements. |
|
QER | Attestation | AutoRemovalScope | GroupMembership | RemoveRequested |
If membership of the system entitlement was requested through the IT Shop, the request is canceled or unsubscribed.
Set the desired behavior in the QER | Attestation | AutoRemovalScope | PWOMethodName configuration parameter. For more information, see Default attestation and withdrawal of entitlements. |
|
QER | Attestation | AutoRemovalScope | GroupMembership | RemoveSystemRole |
System roles incorporating the system entitlements are withdrawn from the employee.
This removes all indirect assignments obtained by the employee through this system role.
This configuration parameter is only available if the System Roles Module is installed. |
|
QER | Attestation | AutoRemovalScope | GroupMembership | RemoveDirectRole |
If membership in the system entitlement was inherited through a secondary role (organization or business role), the employee's membership is removed from this role.
This removes all indirect assignments obtained by the employee through this role. |
|
QER | Attestation | AutoRemovalScope | GroupMembership | RemoveDynamicRole |
If membership in the system entitlement was inherited through a dynamic role, the employee is excluded from the dynamic role.
This removes all indirect assignments obtained by the employee through this role. |
When you use the Attestation of assignments to system entitlements default attestation policy or have set up attestation policies with the Attestation of assignments to system entitlements default attestation procedure, you can configure automatic removal of system entitlements through the QER | Attestation | AutoRemovalScope | UNSGroupInUNSGroup configuration parameter.
Table 43: Effect of configuration parameters when attestation denied
|
QER | Attestation | AutoRemovalScope | UNSGroupInUNSGroup | RemoveDirect |
Assignment of the system entitlement to a system entitlement is removed. |
You can configure automatic withdrawal of system entitlement assignments to hierarchical roles, if you use the following default attestation policies or procedures:
-
Attestation of system entitlement assignments to department
-
Attestation of system entitlement assignments to cost centers
-
Attestation of system entitlement assignments to locations
-
Attestation of system entitlement assignments to business roles
Enabled the following configuration parameters to do this.
Table 44: Effect of configuration parameters when attestation denied
|
QER | Attestation | AutoRemovalScope | DepartmentHasUNSGroup | RemoveDirect |
The assignment of the system entitlement to a department is removed.
Therefore the system entitlement is removed from all employees that inherit assignments from this department. |
|
QER | Attestation | AutoRemovalScope | ProfitCenterHasUNSGroup | RemoveDirect |
The assignment of the system entitlement to a cost center is removed.
Therefore the system entitlement is removed from all employees that inherit assignments from this cost center. |
|
QER | Attestation | AutoRemovalScope | LocalityHasUNSGroup | RemoveDirect |
The assignment of the system entitlement to a location is removed.
Therefore the system entitlement is removed from all employees that inherit assignments from this location. |
|
QER | Attestation | AutoRemovalScope | OrgHasUNSGroup | RemoveDirect |
The assignment of a system entitlement to a business role is removed.
Therefore the system entitlement is removed from all employees that inherit assignments from this business role. |
System role attestation
| Installed modules: |
System Roles Module |
If you use the System role membership attestation default attestation policy or have set up attestation policies with the System entitlement memberships attestation default attestation procedure, you can configure automatic removal of system roles through the QER | Attestation | AutoRemovalScope | ESetAssignment configuration parameter. After attestation approval has been denied, One Identity Manager checks which type of assignment was used for the user account to become a member in the system role.
Table 45: Effect of configuration parameters when attestation denied
|
QER | Attestation | AutoRemovalScope | ESetAssignment | RemoveDirect |
Direct membership in the system role is removed.
This removes all indirect assignments obtained by the employee through this system role. |
|
QER | Attestation | AutoRemovalScope | ESetAssignment | RemovePrimaryRole |
If the system role was inherited through a primary role, the role is withdrawn.
This removes all indirect assignments obtained by the employee through this role. |
|
QER | Attestation | AutoRemovalScope | ESetAssignment | RemoveRequestedRole |
If the system role was inherited through a requested role, the role request is canceled or unsubscribed.
This removes all indirect assignments obtained by the employee through this role.
Set the desired behavior in the QER | Attestation | AutoRemovalScope | PWOMethodName configuration parameter. For more information, see Default attestation and withdrawal of entitlements. |
|
QER | Attestation | AutoRemovalScope | ESetAssignment | RemoveDelegatedRole |
If the system role was inherited through a delegated role, the delegation of this role is canceled or unsubscribed.
This removes all indirect assignments obtained by the employee through this role.
Set the desired behavior in the QER | Attestation | AutoRemovalScope | PWOMethodName configuration parameter. For more information, see Default attestation and withdrawal of entitlements. |
|
QER | Attestation | AutoRemovalScope | ESetAssignment | RemoveRequested |
If the system role was requested through the IT Shop, the request is canceled or unsubscribed.
This removes all indirect assignments obtained by the employee through this system role.
Set the desired behavior in the QER | Attestation | AutoRemovalScope | PWOMethodName configuration parameter. For more information, see Default attestation and withdrawal of entitlements. |
|
QER | Attestation | AutoRemovalScope | ESetAssignment | RemoveDirectRole |
If the system role was inherited through a secondary role (organization or business role), the employee's membership is removed from this role.
This removes all indirect assignments obtained by the employee through this role. |
|
QER | Attestation | AutoRemovalScope | ESetAssignment | RemoveDynamicRole |
If the system role was inherited through a dynamic role, the employee is excluded from the dynamic role.
This removes all indirect assignments obtained by the employee through this role. |
If you use the System role entitlement assignment attestation default attestation policy or have set up attestation policies with the System role entitlement assignment attestation default attestation procedure, you can configure automatic removal of the assignments through the QER | Attestation | AutoRemovalScope | ESetHasEntitlement configuration parameter.
Table 46: Effect of configuration parameters when attestation denied
|
QER | Attestation | AutoRemovalScope | ESetHasEntitlement | RemoveDirect |
Assignment of the company resource to a system role is removed. |
You can configure automatic withdrawal of system role assignments to hierarchical roles, if you use the following default attestation policies or procedures:
-
Department system role assignment attestation
-
Cost center system role assignment attestation
-
Location system role assignment attestation
-
Business role system role assignment attestation
Enabled the following configuration parameters to do this.
Table 47: Effect of configuration parameters when attestation denied
|
QER | Attestation | AutoRemovalScope | DepartmentHasESet | RemoveDirect |
The assignment of the system role to a department is removed.
Therefore the system role is removed from all employees that inherit assignments from this department. |
|
QER | Attestation | AutoRemovalScope | ProfitCenterHasESet | RemoveDirect |
The assignment of the system role to a cost center is removed.
Therefore the system role is removed from all employees that inherit assignments from this cost center. |
|
QER | Attestation | AutoRemovalScope | LocalityHasESet | RemoveDirect |
The assignment of the system role to a location is removed.
Therefore the system role is removed from all employees that inherit assignments from this location. |
|
QER | Attestation | AutoRemovalScope | OrgHasESet | RemoveDirect |
The assignment of the system role to a business role is removed.
Therefore the system role is removed from all employees that inherit assignments from this business role. |
