Bulk Requests and Child Requests

Managing Requests 10-9 Figure 10 3 Bulk Request and Child Request Stages 10-10 Oracle Fusion Middleware Users Guide for Oracle Identity Manager

10.3 Request Models

A request model is a specification that instructs the request management engine to behave in a specific way for a particular request type. Each request must have a request model associated with it. There is a one-to-one relation between a request model and a request type. A request model dictates what information to collect, how to get the approvals, and what action to perform. For example, the information defined for the Create User and Modify User request models are different, and as a result, the actions for each request type are different. Oracle Identity Manager provides a set of predefined request models. Table 10 2 lists the operations and request models that Oracle Identity Manager supports by default. See Also: ■ Table 17–1, Default Request Templates for information about the request models that support bulk request ■ Table 10 1, Request Stages for information about request stages Note: Oracle Identity Manager provides the request models by default. Request models cannot be modified. Table 10 2 Default Operations and Request Models Catalog Request Model Bulk Self or Admin Beneficiary User Management Create User N Admin N Self-Register User N Self N Modify Self Profile N Self N Modify User Profile Y Admin N Enable User Y Admin N Disable User Y Admin N Delete User Y Admin N Provisioning Provision Resource Y Admin Y Self-Request Resource Y Self Y Modify Provisioned Resource Y Admin Y Enable Provisioned Resource Y Admin Y Disable Provisioned Resource Y Admin Y De-Provision Resource Y Admin Y Self Modify Provisioned Resource N Self Y Self De-Provision Resource Y Self Y Role Management Create Role N Admin N Delete Role Y Admin N Modify Role N Admin Y Managing Requests 10-11 In Table 10 2 , the Bulk column indicates the request models for which bulk operations are supported. A bulk request is a request with multiple beneficiaries, multiple target entities, or both. For example, a request to provision multiple roles to user John Doe generates a bulk request. A provisioning request to add users John Doe and Jane Doe to the Managers group also generates a bulk request. A request model is an XML file that specifies how the request must flow after submission, what approvals are required, and what data is required from the requester. It contains the following information: ■ Name of the model ■ Whether or not a target entity is required: The requests in which a resource is provisioned to a user have a beneficiary. An example of this type of request is a request to create an entity and a relationship between a user or organization with that entity. Specifically the relationship is a has a relation. Requests such as creating a user require creation of an entity, but they do not necessarily have a has a relation with any other entity. ■ The beneficiary type that is being addressed, which is user. ■ The entity-type that the model is associated with and whether or not the entity is a generic one. A generic entity type is a parent entity type for which the creation of entities is not possible unless a specific subtype is selected. For example Resource is a generic entity, where E-mail and Laptop are subtypes. If the entity type can be created without defining subtypes, then it is not a generic entity, such as user. ■ Whether or not the model is a creation model. A creation model results in the creation of an entity. It creates an entity and its relation with a user or organization. A non-creation model requires a target entity to be selected. ■ Reference to data collection. A model contains an implicit connection to an XML element to determine the data that needs to be collected. For a generic entity, the final reference is constructed by using the entity subtype selected at runtime, which allows the collection of different data for different entity subtypes. ■ Approval workflow selection. A model may contain a reference to the algorithms that are used to select the approval process to be associated for a request. The parameters to be passed to the algorithm are also mentioned. Assign Roles Y Admin Y Remove from Roles Y Admin Y Self-Assign Role Y Self Y Self-Remove Role Y Self Y Note: For the Create Role, Delete Role, and Modify Role request models, request creation is supported only by using APIs and not from the UI. Table 10 2 Cont. Default Operations and Request Models Catalog Request Model Bulk Self or Admin Beneficiary 10-12 Oracle Fusion Middleware Users Guide for Oracle Identity Manager ■ Whether or not the model supports an operation that is to be performed in bulk mode. ■ Whether or not authentication is required. If true, then a model is available to all authenticated users creating requests. If false, then it is only available through unauthenticated self service, and not available in the authenticated self service.

10.4 Creating Requests for Self and Others

A user logged in to Oracle Identity Manager can create requests from Self Service and Advanced Administration . This section describes how to create requests by using Oracle Identity Manager Self Service in the following topics: ■ Creating a Request to Register Yourself in Oracle Identity Manager ■ Creating a Request from Oracle Identity Manager Self Service

10.4.1 Creating a Request to Register Yourself in Oracle Identity Manager

Using the login page of Oracle Identity Manager Self Service, you can create a request to register yourself in Oracle Identity Manager. This is called a Self-registration request and can be raised by users not present in Oracle Identity Manager anonymous users. To create a Self-registration request:

1. In the login page of Oracle Identity Manager Self Service, click Register. The Step

1: Basic Information page of the User Registration wizard is displayed.

2. Enter first name, last name, and e-mail ID in the respective fields, and then click

Next . The Step 2: Login Information and Security Information page is displayed.

3. In the Select a User ID and Password section, enter login ID and password, and

confirm the password in the respective fields.

4. In the Set your Challenge Questions and Answers section, select challenge

questions and enter answers for the questions. These questions and answers are used if you forget your password and need to reset it.

5. Click Register. A confirmation page is displayed stating that the registration

request is created. This page displays a request tracking number that you can use to check the status of your request.

6. Click Track Registration to track the self registration requests.

10.4.2 Creating a Request from Oracle Identity Manager Self Service

Oracle Identity Manager Self Service allows you to create requests from the Welcome page, the My Requests page, and the My Profile page, as described in the following sections: ■ Creating a Request From Welcome Page of Oracle Identity Manager Self Service ■ Creating a Request From the My Requests Page ■ Creating a Request From the My Profile Page See Also: Creating Requests by Using Oracle Identity Manager Advanced Administration on page 14-1 for information about creating requests as a request administrator by using the Advanced Administration UI