Chat now with support
Chat with Support

Identity Manager 8.0 - Attestation Administration Guide

Attestation and Recertification
One Identity Manager Users for Attestation Attestation Base Data Attestation Policies Creating Custom Mail Templates for Notifications
Approval Processes for Attestation Cases
Approval Policies Approval Workflows Selecting Attestors Setting up Multi-Factor Authentication for Attestation Prevent Attestation by Employee Awaiting Attestation Managing Attestation Cases
Attestation Sequence Default Attestation and Withdrawal of Entitlements User Attestation and Recertification Mitigating Controls Configuration Parameters for Attestation

Finding Attestors from Product Owners

If service items or system entitlements need to be attested, product owners can be determined as attestors. Use the approval procedure "OA" to do this. Any number of service items and system entitlements which are assigned a service item can be attested.

Assign an application role to the service item in Product owner. This determines all employees as attestor who have the given application role.

Calculated approval

Calculated approval

NOTE: Only one approval step can be defined with the approval procedure "CD" per approval level.

If you want to make attestation dependent on specific conditions, use the approval procedure "CD". This procedure does not determine an attestor. The One Identity Manager makes the decision depending on the condition that is formulated in the approval step.

You can use the procedure for any attestation base objects. You create a condition in the approval step. If the condition returns a result, the approval step is approved through the One Identity Manager. If the condition does not return a result, the approval step is denied by the One Identity Manager. If there are no further approval steps, the approval procedure is either finally granted or denied.

To enter a condition for the approval procedure "CD"

  1. Edit the approval step properties.

    For more information, see Editing Approval Levels.

  2. Enter a valid WHERE clause for the database query in Condition or Condition (Oracle). You can enter the SQL query directly or with a wizard. Refer to the condition using the variable '@UID_AttestationCase' (SQL) or 'v_uid_attestationcase' (Oracle) in the definite case of an attestation instance.
Example of a simple approval workflow with the approval procedure CD:

Compliance should be tested when they meet the following conditions:

  1. Compliance rule is enabled
  2. A rule manager is assigned to the compliance rule

Find the objects that meet these conditions by using the approval procedure CD.


(SELECT 1 FROM (SELECT xobjectkey FROM ComplianceRule

WHERE isnull(IsWorkingCopy, 0) = 0 AND EXISTS


as X WHERE X.UID_AERole = ComplianceRule.UID_OrgResponsible))

as X WHERE X.xobjectkey = AttestationCase.ObjectKeyBase)

If the condition is met, the rule attestor should attest this compliance rule. To do this, extend the positive approval path with an approval step using approval procedure "AR".

If the condition is not met, the attestation should be denied by the One Identity Manager. In this case, no further approval steps are required.

Making External Approvals

Making External Approvals

Use external approvals (approval procedure "EX") if an attestation needs to be approved once a defined event from outside the One Identity Manager takes place. You can also use this procedure to allow any number of objects to be attested by employees that do not have access to the One Identity Manager.

Specify an event in the approval step that triggers an external approval. A process is started by the event that initiates the external approval for the attestation case and evaluates the result of the approval decision. The approval process waits for the external decision to be passed to One Identity Manager. Define the subsequent approval steps depending on the result of the external approval.

To use an approval procedure

  1. Define your own processes that:
    • Trigger an external approval
    • Analyze the results of the external approval
    • Subsequently grant or deny approval for the external approval step in One Identity Manager
  2. Define an event, which starts the process for external approval. Enter the result in Result in the approval step.

If the external event occurs, the approval step status in One Identity Manager has to be changed. Use the process task CallMethod with the method MakeDecision for this. Pass the following parameters to the process task:

MethodName: Value = "MakeDecision"

ObjectType: Value = "AttestationCase"

Param1: Value = "sa"

Param2: Value = <approval> ("true" = granted; "false" = denied)

Param3: Value = <reason for approval decision>

Param4: Value = <standard reason>

Param5: Value = <number approval steps> (PWODecisionStep.SubLevelNumber)

WhereClause: Value = "UID_AttestationCase ='"& $UID_AttestationCase$ &"'"

Use these parameters to specify which attestation case is approved by external approval (whereClause). Parameter param 1 specifies the attestor. Attestor is always the system user "sa". Parameter param 2 is passed to the approval. If the attestation was granted approval the value must be "true". If the attestation was denied approval the value must be "false". Use parameter Param3 to pass a reason text fro the approval decision; use Param4 to pass a predefined standard reason. If more than one external approval steps have been defined in an approval level, use Param5 to pass the approval step count. This ensures the approval is aligned with the correct approval step.

Use the Process Editor to define and edit processes.


All compliance rules should be checked and attested by an external assessor. The attestation object data should be made available as a PDF on an external share. The assessor should save the result of the attestation in a text file on the external share. Use this approval procedure to make external approvals and define:

  • A process "P1" that saves a PDF report with data about the attestation object data and the attestation procedure on an external share
  • An event "E1" that starts the process "P1".

    Enter the event "E1" in the approval step in the Event field and in the process "P1" as a trigger event for external approval.

  • A process "P2" that checks the share for new text files, evaluates the content and calls the One Identity Manager task CallMethod with the method MakeDecision
  • An event "E2" that starts the process "P2"
  • A schedule that starts the events "E2" on a regular basis

For more detailed information about creating processes and schedules, see the One Identity Manager Configuration Guide.

Detailed information about this topic

Deferring Attestation

Deferring Attestation

NOTE: Only one approval step can be defined with the approval procedure "WC" per approval level.

If you want to ensure that a specific data state exists in the One Identity Manager before attestation, then use the approval procedure "WC". Use a condition to specify which prerequisites have to be fulfilled so that attestation can take place. The condition is evaluated as a function call. The function has to accept the attestation case UID as a parameter (AttestationCase.UID_AttestationCase). Use this UID to refer to each attestation object. It must define three return values as integers. One of the following actions is carried out depending on the function‘s return value:

Table 28: Return Value for Deferred Approval
Return value Action

Return value > 0

The condition is fulfilled. Deferred approval has completed successfully. The next approval step (in case of success) is carried out.

Return value = 0

The condition is not yet fulfilled. Approval is rolled back and is retested the next time DBQueue Processor runs.

Return value < 0

The condition is not fulfilled. Deferred approval has failed. The next approval step (in case of failure) is carried out.

To use an approval procedure

  1. Create a database function, which tests the condition for the attestation.
  2. Create an approval step with the approval procedure "CW". Enter the function call in Condition.
    Table 29: Syntax for the function call
    SQL Server:

    dbo.<function name>

    Oracle Database:

    <database schema name>.<function name>

  3. Specify an approval step in the case of success. Use the approval procedure with which One Identity Manager can determine the attestors.
  4. Specify an approval step in the case of failure.
Related Documents