On the Resource Object tab, create the ActDir resource object for trusted source

Developing Resource Objects 11-81 4. After you have added the fields and the reconciliation rules, delete the Lotus Notes-specific fields and the corresponding rules created in the Xellerate User resource object. 5. Create the LotNotes process definition in the Process Definition form. For detailed information about the procedure to create a process definition, see Process Definition Form on page 12-5. Based on the Xellerate User reconciliation field mappings, on the Reconciliation Field Mappings tab, add the field mappings for the LotNotes process definition. 6. Delete the Lotus Notes-specific field mappings in the Xellerate User resource object. For both Active Directory and Lotus Notes, perform the rest of the steps required to configure trusted source reconciliation. For example, while configuring the reconciliation scheduled task for each connector, specify the name of the trusted source resource object that must be used during reconciliation. The current value of the scheduled task attribute would be Xellerate User and it must be updated with the name of the new resource object configured for trusted source user reconciliation for this connector. Figure 11–40 shows the design time implementation of trusted source reconciliation of specific OIM User attributes. Figure 11–40 Trusted Source Reconciliation for Specific OIM User Attributes

11.9.5 Service Account Management

Oracle Identity Manager supports service accounts. Service accounts are general administrator accounts for example, admin1, admin2, admin3, and so on that are used for maintenance purposes, and are typically shared by a set of users. The model for managing and provisioning service accounts is slightly different from normal provisioning. Service accounts are requested, provisioned, and managed in the same manner as regular accounts. They use the same resource objects, provisioning processes, and 11-82 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager process forms as regular accounts. A service account is distinguished from a regular account by an internal flag. When a user is provisioned with a service account, Oracle Identity Manager manages a mapping from the users identity to the service account. When the resource is revoked, or the user gets deleted, the provisioning process for the service account does not get canceled which would cause the undo tasks to start. Instead, a task is inserted into the provisioning process the same way Oracle Identity Manager handles Disable and Enable actions. This task removes the mapping from the user to the service account, and returns the service account to the pool of available accounts. This management capability is available through APIs.