Searching Attestation Tasks Managing Attestation Tasks

9-16 Oracle Fusion Middleware Users Guide for Oracle Identity Manager Table 9 6 lists the fields in the Attestation Request Detail window: Table 9 6 Fields in the Attestation Request Detail Window Field Description Process Name of your attestation process created. Request Time The time when the request is created. Hide records where action has already been specified Whether or not the records for which action has been specified must be hidden from the list of attestation requests. User User whose entitlement is being attested. The data is displayed as a link. When you click the link, the user profile page is displayed with the user details for the attestation date. Resource Resource that is the basis for the entitlement being attested. The data is displayed as a link. When you click the link, a page is displayed with the process form data of the entitlement for the attestation date. Descriptive Data Description of the provisioned resource instance. Last Attested Last response that was provided for the attestation. Comments Reviewer comments. The comments will be updated in this field, when you click Update Existing Comments and Delegation Information . Long comments are truncated, and tooltips are used to show the full text of the comments. Actions Action to be performed on the request. The value can be one of the following: ■ Certify ■ Reject ■ Decline ■ Delegate Submit Attestation Click this button to submit the attestation request. Save Click this button to save the attestation request for future submission. 10 Managing Requests 10-1 10 Managing Requests In Oracle Identity Manager, various operations, such as creating a user or provisioning a resource, can be performed through requests. A request is an entity created by the users or administrators performing a specific action that requires a discretionary permission to be gained by someone or some process before the action can be performed. For example, a user can create a request to gain access to a laptop computer and a manager can create an open requisition based on the request. A request has a requester, a beneficiary optional, and a target entity. A requester is an entity that creates or raises a request. A requester can be a user or the system itself. The functional component decides on the requester for system-generated requests. An example of a system-generated request is a request created by the system based on access policy. Here, the functional component is access policy. For unauthenticated requests, the requester is not authenticated to Oracle Identity Manager and is therefore, not present in the system. A beneficiary is an entity that benefits from the action performed after the request is completed and the request is completed only if it is executed successfully. In Oracle Identity Manager, terms such as user, organization, roles, and resources are defined as entities. Each one of these entities maintains a list of attributes belonging to this entity. Each entity also defines a list of operations that it supports. Target entity is the resource that is requested for the beneficiary. For instance, you create a request to provision a UNIX account for the user John Doe. Here, you are the requester, John Doe is the beneficiary, and the UNIX account is the target entity that is requested for John Doe. Each request goes through a specific lifecycle after it is created in the system. This lifecycle is managed and controlled by the Request Service. The lifecycle transitions the request through various stages. The stage that a request is in determines what action the controller takes in that step, what operations are available on the request, and what possible stage the transitions are in at that time. Figure 10 1 outlines the process flow of a request: