This chapter is divided into the following sections:
Apply the following guidelines while using the connector:
If you have configured Sun Java System Directory for target resource reconciliation, then while manually creating a user account in Sun Java System Directory through Oracle Identity Manager, you must ensure that the user ID in the process form is the same as the Oracle Identity Manager user login. Otherwise, reconciliation of the following operations would fail because these operations require direct API calls to update the information:
Enable status of user
Disable status of user
Organization update
The user search is based on the user ID only.
During provisioning, you cannot use non-English characters for the password of the user. This is because Sun Java System Directory does not support non-ASCII characters in the Password field.
During provisioning, you cannot use non-ASCII characters for the user ID or e-mail address of the user. This is because, by default, Sun Java System Directory does not permit the entry of non-ASCII characters in the User ID and E-mail fields. If you want to enable the entry of non-ASCII characters in these fields, then see Section 3.1.1, "Enabling the Entry of Non-ASCII Characters in the User ID and E-mail Fields".
If you are using Sun ONE Directory Server 5.2:
Open Sun ONE Directory Server.
Click the Configuration tab.
Expand Plugins.
Select 7-bit check.
Deselect the Enable plug-in check box.
Click Save.
If you are using Sun Java System Directory Server Enterprise Edition 6.3:
Click the Directory Servers tab.
Select the server that is currently in use and ensure it is in the Started state.
Click the Server Configuration tab.
Click Plugins.
Select 7-Bit check.
Deselect the Enable plug-in check box.
First-time or full reconciliation involves reconciling all existing user records from the target system into Oracle Identity Manager. The following is the sequence of steps involved in reconciling all existing user records:
Note:
In Oracle Identity Manager release 11.1.1, a scheduled job is an instance of a scheduled task. In this guide, the term scheduled task used in the context of Oracle Identity Manager release 9.1.0.x is the same as the term scheduled job in the context of Oracle Identity Manager release 11.1.1.
See Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager for more information about scheduled tasks and scheduled jobs.
Perform lookup field synchronization by running the scheduled tasks provided for this operation.
See Section 3.3, "Lookup Field Synchronization" for information about the attributes of the scheduled tasks for lookup field synchronization.
See Section 3.5, "Configuring Scheduled Tasks" for information about running scheduled tasks.
Perform user reconciliation by running the scheduled task for user reconciliation.
See Section 3.4.3, "Reconciliation Scheduled Tasks" for information about the attributes of this scheduled task.
See Section 3.5, "Configuring Scheduled Tasks" for information about running scheduled tasks.
After first-time reconciliation, depending on the mode in which you configure the connector, one of the following parameters of the Sun Java System Directory IT Resource IT resource is automatically set to the time stamp at which the reconciliation run began:
For trusted source reconciliation, the Last Recon Trusted TimeStamp parameter is set.
For target resource reconciliation, the Last Recon Target TimeStamp parameter is set.
See Also:
Section 2.2, "Installation" for information about the parameters of the IT resource
From the next reconciliation run onward, only target system user records that are added or modified after the time stamp stored in the IT resource are considered for incremental reconciliation. These records are brought to Oracle Identity Manager when you configure and run the user reconciliation scheduled task.
The following scheduled tasks are used for lookup fields reconciliation:
iPlanet Organization Lookup Reconciliation
iPlanet Role Lookup Reconciliation
iPlanet Group Lookup Reconciliation
You must specify values for the attributes of these scheduled tasks. Table 3-1 describes the attributes of these scheduled tasks. Section 3.5, "Configuring Scheduled Tasks" describes the procedure to configure scheduled tasks.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.
Values (either default or user-defined) must be assigned to all the attributes. If even a single attribute value were left empty, then reconciliation would not be performed.
Table 3-1 Attributes of the Scheduled Tasks for Lookup Field Synchronization
| Attribute | Description | Default/Sample Value |
|---|---|---|
|
LookupCodeName |
Name of the lookup definition to which values are to be reconciled |
The value is one of the following:
|
|
ITResourceName |
Name of the IT resource for setting up a connection with Sun Java System Directory |
|
|
SearchContext |
Search context to be used for searching for users |
|
|
Lookup Search Filter |
Search filter in LDAP format |
The value is one of the following:
|
|
ReconMode |
Specify Specify |
|
|
AttrName for Decode Value in Lookup |
Attribute type of group, role, or organization that should be populated in the Decode value from the target system. It can be either |
This value can be any attribute name in the target entry. |
|
AttrName for Code value in Lookup |
Attribute type of group, role, or organization that should be populated in the Code Key value from the target system. |
The default value is Note: You must not change this value. |
|
ConfigurationLookup |
Name of the lookup definition that stores configuration information used during connector operations Do not change the default value. |
|
Reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to user accounts on the target system. This section discusses the following topics related to configuring reconciliation:
Note:
By default, the target system server has a limitation on the maximum number of users whose data can be reconciled. If you want to reconcile user data in bulk amounts exceeding the maximum limit allowed by the target system server, then perform the following:
Open the Sun ONE Directory Server console.
Click the Configuration tab.
Select Performance on the left panel. On the Client Control tab, select the Unlimited check boxes for the Size limit and Look-through limit fields.
By default, all target system records that are added or modified after the last reconciliation run are reconciled during the current reconciliation run. You can customize this process by specifying the subset of added or modified target system records that must be reconciled. You do this by creating filters for the reconciliation module.
For this connector, you create a filter by specifying a value for the searchfilter attribute while configuring the scheduled task for user reconciliation.
You can use the Sun Java System Directory attributes to build a query condition. You specify this query condition as the value of the searchfilter attribute.
The following are sample query conditions that can be specified as the value of the searchfilter attribute:
(&(objectClass=inetOrgPerson)(givenname=John))
(&(objectClass=inetOrgPerson)(sn=Doe))
(&(&(sn=Doe)(givenname=John))(objectClass=inetOrgPerson))
(|(|(sn=lastname)(givenname=firstname))(objectClass=inetOrgPerson))
Other target system attributes, such as cn, uid, and mail, can also be used to build the query condition.
When you specify a value for the searchfilter attribute, then only the records that meet both of the following criteria are reconciled:
Records that meet the matching criteria specified by the searchfilter attribute
Records that are added or updated after the time-stamp value specified by the time-stamp IT resource parameter
Note:
As mentioned earlier in the guide, the value of the time-stamp IT resource parameter is automatically updated by Oracle Identity Manager. You must not change the value of this parameter.
The following are guidelines to be followed while specifying a value for the searchfilter attribute:
For the Sun Java System Directory attributes, you must use the same case (uppercase or lowercase) as given in the target system. This is because attribute names are case-sensitive.
You must not include unnecessary blank spaces between operators and values in the query condition.
A query condition with spaces separating values and operators would yield different results as compared to a query condition that does not contain spaces between values and operators.
You must enclose the query condition in parentheses. For example:
(&(objectClass=user)(sn!=Doe))
You must not include special characters other than the equal sign (=), ampersand (&), vertical bar (|), and parentheses (()) in the query condition.
Note:
An exception is thrown if you include special characters other than the ones specified here.
As mentioned earlier in this section, you specify a value for the searchfilter attribute while configuring the scheduled task for user reconciliation.
During a reconciliation run, all changes in the target system records are reconciled into Oracle Identity Manager. Depending on the number of records to be reconciled, this process may require a large amount of time. In addition, if the connection breaks during reconciliation, then the process would take longer to complete.
You can configure batched reconciliation to avoid such problems.
To configure batched reconciliation, you use the BatchSize user reconciliation scheduled task attribute. This attribute is used to specify the number of records that must be included in each batch fetched from the target system.
Note:
You must specify a numeric value for the BatchSize attribute.
If you specify 0 as the value, then all records are fetched from the target system. In other words, batched reconciliation is not performed.
Caution:
For reconciliation of deleted users, you must accept the default value of 0. If you change this value, then records of existing users will be deleted from Oracle Identity Manager.
You specify a value for the BatchSize attribute while performing the procedure described in the Section 3.4.3.1, "User Reconciliation Scheduled Task."
After you configure batched reconciliation, if reconciliation fails during a batched reconciliation run, then refer to the log file for information about the batch at which reconciliation has failed. The log file provides the following information about batched reconciliation:
Serial numbers of the batches that have been successfully reconciled
User IDs associated with the records with each batch that has been successfully reconciled
If the batched reconciliation run fails, then the serial number of the batch that has failed
This section discusses the following topics:
The following scheduled tasks are used for user reconciliation:
iPlanet User Trusted Recon Task
iPlanet User Target Recon Task
iPlanet Target Delete User Recon Task
iPlanet Trusted Delete User Recon Task
You must specify values for the attributes of these scheduled tasks. Table 3-2 describes the attributes of these scheduled tasks.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.
Values (either default or user-defined) must be assigned to all the attributes. If even a single attribute value were left empty, then reconciliation would not be performed.
Table 3-2 Attributes of the User Reconciliation Scheduled Tasks
| Attribute | Description | Default/Sample Value |
|---|---|---|
|
BatchSize |
This attribute is used for batched reconciliation. It specifies the number of records that must be included in each batch. Caution: For reconciliation of deleted users, you must accept the default value of 0. If you change this value, then records of existing users will be deleted from Oracle Identity Manager. See Also: Section 3.4.2, "Batched Reconciliation" |
Default value: |
|
ConfigurationLookup |
Name of the lookup definition that stores configuration information used during connector operations Do not change the default value. |
|
|
ITResourceName |
Name of the IT resource for setting up a connection with Sun Java System Directory |
|
|
Organization |
Name of the organization in Oracle Identity Manager to which you want to reconcile users Note: This attribute is specific to the |
|
|
Role |
Name of the role in Oracle Identity Manager that you want to assign to newly reconciled users Note: This attribute is specific to the iPlanet User Trusted Recon Task scheduled task. |
|
|
SearchBase |
DN in which the search for user accounts is rooted in Note: For the iPlanet Target Delete User Recon Task and iPlanet Trusted Delete User Recon Task scheduled tasks, ensure that the value of this attribute is |
For Delete Recon scheduled task:
|
|
SearchFilter |
LDAP search filter used to locate an organization accounts See Section 3.4.1, "Limited Reconciliation" for more information. |
For Delete Recon scheduled task:
|
|
SearchScope |
Search scope used to locate user accounts Note: For the iPlanet Target Delete User Recon Task and iPlanet Trusted Delete User Recon Task scheduled tasks, ensure that the value of this attribute is |
|
|
TrustedResourceObjectName |
Name of the resource object for trusted source user reconciliation and deleted user reconciliation Note: This attribute is specific to the iPlanet User Trusted Recon Task and iPlanet Trusted Delete User Recon Task scheduled tasks. |
|
|
TargetResourceObjectName |
Name of the resource object for target resource user reconciliation and deleted user reconciliation Note: This attribute is specific to the iPlanet User Target Recon Task and iPlanet Target Delete User Recon Task scheduled tasks. |
|
The following scheduled tasks are used for group and role reconciliation:
Note:
You cannot reconcile group data and role data from the target system if you are using Oracle Identity Manager release 11.1.1. This issue is tracked by Bug 9799541 in Chapter 6, "Known Issues."
iPlanet Group Recon Task
iPlanet Role Recon Task
You must specify values for the attributes of these scheduled tasks. Table 3-3 describes the attributes of these scheduled tasks.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.
Values (either default or user-defined) must be assigned to all the attributes. If even a single attribute value were left empty, then reconciliation would not be performed.
Table 3-3 Attributes of the Group and Role Reconciliation Scheduled Tasks
| Attribute | Description | Default/Sample Value |
|---|---|---|
|
ConfigurationLookup |
Name of the lookup definition that stores configuration information used during connector operations Do not change the default value. |
|
|
Field Lookup Code |
Name of the lookup definition that stores reconciliation field mappings for group or role connector operations Provide the corresponding reconciliation look up mappings |
For Role:
For Group:
|
|
isRoleRecon |
Specifies if the recon is group or role reconciliation If it is group recon it is |
For Role:
For Group:
|
|
ITResourceName |
Name of the IT resource for setting up a connection with Sun Java System Directory |
|
|
MultiValued Attributes |
Set of multivalued attributes are added here separated by the | operator Example: <phones|pager> |
|
|
ResourceObjectName |
Name of the resource object for reconciliation of Group or Role |
For Role:
For Group:
|
|
SearchBase |
DN in which the search for Group or Role is rooted in |
|
|
SearchFilter |
LDAP search filter used to locate Group or Role |
For Role:
For Group:
|
You can apply the procedure described in this section to configure the scheduled tasks for lookup field synchronization and reconciliation.
Table 3-4 lists the scheduled tasks that form part of the connector.
Table 3-4 Scheduled Tasks for Lookup Field Synchronization and Reconciliation
| Scheduled Task | Description |
|---|---|
|
iPlanet Organization Lookup Reconciliation |
This scheduled task is used for organization lookup field synchronization. See Section 3.3, "Lookup Field Synchronization" for information about this scheduled task. |
|
iPlanet Role Lookup Reconciliation |
This scheduled task is used for role lookup field synchronization. See Section 3.3, "Lookup Field Synchronization" for information about this scheduled task. |
|
iPlanet Group Lookup Reconciliation |
This scheduled task is used for group lookup field synchronization. See Section 3.3, "Lookup Field Synchronization" for information about this scheduled task. |
|
iPlanet User Trusted Recon Task |
This scheduled task is used for user reconciliation when the target system is configured as a trusted source. See Section 3.4.3, "Reconciliation Scheduled Tasks" for information about this scheduled task. |
|
iPlanet User Target Recon Task |
This scheduled task is used for user reconciliation when the target system is configured as a target resource. See Section 3.4.3, "Reconciliation Scheduled Tasks" for information about this scheduled task. |
|
iPlanet Trusted Delete User Recon Task |
This scheduled task is used for reconciliation of deleted users when the target system is configured as a trusted source. See Section 3.4.3, "Reconciliation Scheduled Tasks" for information about this scheduled task. |
|
iPlanet Target Delete User Recon Task |
This scheduled task is used for reconciliation of deleted users when the target system is configured as a target resource. See Section 3.4.3, "Reconciliation Scheduled Tasks" for information about this scheduled task. |
|
iPlanet Group Recon Task |
This scheduled task is used for reconciliation of groups from the target system. See Section 3.4.3, "Reconciliation Scheduled Tasks" for information about this scheduled task. |
|
iPlanet Role Recon Task |
This scheduled task is used for reconciliation of roles from the target system. See Section 3.4.3, "Reconciliation Scheduled Tasks" for information about this scheduled task. |
Depending on the Oracle Identity Manager release that you are using, perform the procedure described in one of the following sections:
To configure the reconciliation scheduled task:
Expand the Xellerate Administration folder.
Click Find. The details of the predefined scheduled tasks are displayed.
Enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager must attempt to complete the task before assigning the ERROR status to the task.
Ensure that the Disabled and Stop Execution check boxes are not selected.
In the Start region, double-click the Start Time field. From the date-time editor that is displayed, select the date and time at which you want the task to run.
In the Interval region, set the following schedule parameters:
To set the task to run on a recurring basis, select the Daily, Weekly, Recurring Intervals, Monthly, or Yearly option.
If you select the Recurring Intervals option, then you must also specify the time interval at which you want the task to run on a recurring basis.
To set the task to run only once, select the Once option.
Provide values for the user-configurable attributes of the scheduled task.
See Also:
Oracle Fusion Middleware User's Guide for Oracle Identity Manager for information about adding and removing task attributes
Click Save. The scheduled task is created. The INACTIVE status is displayed in the Status field, because the task is not currently running. The task is run at the date and time that you set in Step 7.
Suppose the user reconciliation scheduled task for the connector is running and user records are being reconciled. If you want to stop the reconciliation process:
To configure scheduled tasks:
Log in to the Administrative and User Console.
Do one of the following:
If you are using Oracle Identity Manager release 9.1.0.x, expand Resource Management, and then click Manage Scheduled Task.
If you are using Oracle Identity Manager release 11.1.1, then on the Welcome to Oracle Identity Manager Self Service page, click Advanced in the upper-right corner of the page.
Search for and open the scheduled task as follows:
If you are using Oracle Identity Manager release 9.1.0.x, then:
On the Scheduled Task Management page, enter the name of the scheduled task as the search criteria and then click Search.
In the search results table, click the edit icon in the Edit column for the scheduled task.
On the Scheduled Task Details page where the details of the scheduled task that you selected is displayed, click Edit.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome to Oracle Identity Manager Advanced Administration page, in the System Management region, click Search Scheduled Jobs.
On the left pane, in the Search field, enter the name of the scheduled job as the search criterion. Alternatively, you can click Advanced Search and specify the search criterion.
In the search results table on the left pane, click the scheduled job in the Job Name column.
Modify the details of the scheduled task. To do so:
If you are using Oracle Identity Manager release 9.1.0.x, then on the Edit Scheduled Task Details page, modify the following parameters, and then click Continue:
Status: Specify whether you want to leave the task in the enabled state. In the enabled state, the task is ready for use.
Max Retries: Enter an integer value in this field. This number represents the number of times Oracle Identity Manager must attempt to complete the task before assigning the ERROR status to the task. The default value is 1.
Next Start: Use the date editor to specify the date when you want the task to run. After you select a date value in the date editor, you can modify the time value that is automatically displayed in the Next Start field.
Frequency: Specify the frequency at which you want the task to run.
If you are using Oracle Identity Manager release 11.1.1, then on the Job Details tab, you can modify the following parameters:
Retries: Enter an integer value in this field. This number represents the number of times the scheduler tries to start the job before assigning the Stopped status to the job.
Schedule Type: Depending on the frequency at which you want the job to run, select the appropriate schedule type.
Note:
See Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager for detailed information about schedule types.
In addition to modifying the job details, you can enable or disable a job.
Specify values for the attributes of the scheduled task. To do so:
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.
Values (either default or user-defined) must be assigned to all the attributes. If even a single attribute value is left empty, then reconciliation is not performed.
If you are using Oracle Identity Manager release 9.1.0.x, then on the Attributes page, select the attribute from the Attribute list, specify a value in the field provided, and then click Update.
If you are using Oracle Identity Manager release 11.1.1, then on the Job Details tab, in the Parameters region, specify values for the attributes of the scheduled task.
After specifying the attributes, do one of the following:
If you are using Oracle Identity Manager release 9.1.0.x, then click Save Changes to save the changes.
Note:
The Stop Execution option is not available in the Administrative and User Console. If you want to stop a task, then click Stop Execution on the Task Scheduler form of the Design Console.
If you are using Oracle Identity Manager release 11.1.1, then click Apply to save the changes.
Note:
The Stop Execution option is available in the Administrative and User Console. You can use the Scheduler Status page to either start, stop, or reinitialize the scheduler.
Provisioning involves creating or modifying a user's account information on the target system through Oracle Identity Manager.
This section discusses the following topics related to configuring provisioning:
Section 3.6.2, "Provisioning Organizational Units, Groups, and Roles"
Section 3.6.3, "Enabling Provisioning of Users in Organizations and Organizational Units"
Provisioning a resource for an OIM User involves using Oracle Identity Manager to create a target system account for the user.
When you install the connector on Oracle Identity Manager release 11.1.1, the direct provisioning feature is automatically enabled. This means that the process form is enabled when you install the connector.
If you have configured the connector for request-based provisioning, then the process form is suppressed and the object form is displayed. In other words, direct provisioning is disabled when you configure the connector for request-based provisioning. If you want to revert to direct provisioning, then perform the steps described in Section 3.7, "Switching Between Request-Based Provisioning and Direct Provisioning on Oracle Identity Manager Release 11.1.1."
This following are types of provisioning operations:
See Also:
Oracle Identity Manager Connector Concepts for information about the types of provisioning
This section discusses the following topics:
To provision a resource by using the direct provisioning approach:
Log in to the Administrative and User Console.
If you want to first create an OIM User and then provision a target system account, then:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, then:
From the Users menu, select Create.
On the Create User page, enter values for the OIM User fields and then click Create User.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome to Identity Administration page, in the Users region, click Create User.
On the Create User page, enter values for the OIM User fields, and then click Save.
If you want to provision a target system account to an existing OIM User, then:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, then:
From the Users menu, select Manage.
Search for the OIM User and select the link for the user from the list of users displayed in the search results.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome to Identity Administration page, search for the OIM User by selecting Users from the list on the left pane.
From the list of users displayed in the search results, select the OIM User. The user details page is displayed on the right pane.
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, then:
On the User Detail page, select Resource Profile from the list at the top of the page.
On the Resource Profile page, click Provision New Resource.
If you are using Oracle Identity Manager release 11.1.1, then:
On the user details page, click the Resources tab.
From the Action menu, select Add Resource. Alternatively, you can click the add resource icon with the plus (+) sign. The Provision Resource to User page is displayed in a new window.
On the Step 1: Select a Resource page, select iPlanet User from the list and then click Continue.
On the Step 2: Verify Resource Selection page, click Continue.
On the Step 5: Provide Process Data for iPlanet User Details page, enter the details of the account that you want to create on the target system and then click Continue.
On the Step 5: Provide Process Data for iPlanet User Group Membership Details page, search for and select a group for the user on the target system and then click Continue.
On the Step 6: Verify Process Data page, verify the data that you have provided and then click Continue.
The "Provisioning has been initiated" message is displayed. Perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, click Back to User Resource Profile. The Resource Profile page shows that the resource has been provisioned to the user.
If you are using Oracle Identity Manager release 11.1.1, then:
Close the window displaying the "Provisioning has been initiated" message.
On the Resources tab, click Refresh to view the newly provisioned resource.
Note:
The information provided in this section is applicable only if you are using Oracle Identity Manager release 11.1.1.
A request-based provisioning operation involves both end users and approvers. Typically, these approvers are in the management chain of the requesters. The following sections discuss the steps to be performed by end users and approvers during a request-based provisioning operation:
Note:
The procedures described in these sections are built on an example in which the end user raises or creates a request for provisioning a target system account. This request is then approved by the approver.
Section 3.6.1.2.1, "End User's Role in Request-Based Provisioning"
Section 3.6.1.2.2, "Approver's Role in Request-Based Provisioning"
The following steps are performed by the end user in a request-based provisioning operation:
See Also:
Oracle Fusion Middleware User's Guide for Oracle Identity Manager for detailed information about these steps
Log in to the Administrative and User Console.
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Identity Administration page, click the Administration tab, and then click the Requests tab.
From the Actions menu on the left pane, select Create Request.
The Select Request Template page is displayed.
From the Request Template list, select Provision Resource and click Next.
On the Select Users page, specify a search criterion in the fields to search for the user that you want to provision the resource, and then click Search. A list of users that match the search criterion you specify is displayed in the Available Users list.
From the Available Users list, select the user to whom you want to provision the account..
If you want to create a provisioning request for more than one user, then from the Available Users list, select users to whom you want to provision the account.
Click Move or Move All to include your selection in the Selected Users list, and then click Next.
On the Select Resources page, click the arrow button next to the Resource Name field to display the list of all available resources.
From the Available Resources list, select iPlanet User, move it to the Selected Resources list, and then click Next.
On the Resource Details page, enter details of the account that must be created on the target system, and then click Next.
On the Justification page, you can specify values for the following fields, and then click Finish.
Effective Date
Justification
On the resulting page, a message confirming that your request has been sent successfully is displayed along with the Request ID.
If you click the request ID, then the Request Details page is displayed.
To view details of the approval, on the Request Details page, click the Request History tab.
The following are steps performed by the approver in a request-based provisioning operation:
The following are steps that the approver can perform:
Log in to the Administrative and User Console.
On the Welcome page, click Self-Service in the upper-right corner of the page.
On the Welcome to Identity Manager Self Service page, click the Tasks tab.
On the Approvals tab, in the first section, you can specify a search criterion for request task that is assigned to you.
From the search results table, select the row containing the request you want to approve, and then click Approve Task.
A message confirming that the task was approved is displayed.
See Also:
Oracle Fusion Middleware User's Guide for Oracle Identity Manager for detailed information about these steps
To provision an organizational unit:
Log in to the Oracle Identity Manager Administrative and User Console.
Create an organization. To do so:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, then:
Expand Organizations, and then click Create.
Specify a name and the type for the organization that you want to create, and then click Create Organization.
The organization is created.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome page, click Administration in the upper-right corner of the page.
On the Welcome to Identity Administration page, from the Organizations section, click Create Organization.
On the Create Organization page, enter values for the Name, Type, and Parent Organization (optional) fields, and then click Save.
The organization is created.
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, then:
Select Resource Profile from the list.
Click Provision New Resource.
The Provision Resource to Organization page is displayed.
If you are using Oracle Identity Manager release 11.1.1, then:
On the organization details page, click the Resources tab.
From the Actions menu, select Provision. Alternatively, click Provision on the toolbar. The Provision Resource to Organization page is displayed in a new window.
On the Step 1: Select a Resource page, search for and select the organizational unit you want to provision, and then click Continue.
On the Step 2: Verify Resource Selection page, verify the data that you provided, and then click Continue.
On the Step 5: Provide Process Data page, enter the details of the organizational unit that you want to provision and then click Continue.
On the Step 6: Verify Process Data page, verify the data that you have provided and then click Continue.
The "Provisioning has been initiated" message is displayed. Perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, click Back to User Resource Profile. The Resource Profile page shows that the organizational unit has been provisioned to the organization.
If you are using Oracle Identity Manager release 11.1.1, then:
Close the window displaying the "Provisioning has been initiated" message.
On the Resources tab, click Refresh to view the newly provisioned organizational unit.
To provision a group or role:
Log in to the Oracle Identity Manager Administrative and User Console.
Search for and open the organization to which you want to provision a group or role by performing one of the following steps:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, then:
From the Organizations menu, select Manage.
Search for the organization and select the link for the organization from the list of organizations displayed in the search results.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome to Identity Administration page, in the Organizations section, click Advanced Search - Organizations, provide a search criterion, and then click Search.
Alternatively, search for the organization by selecting Organizations from the list on the left pane.
From the organizations displayed in the search results table, click the row containing the organization to which to want to provision a group or role.
The organization details page is displayed.
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, then:
On the Organization Detail page, select Resource Profile from the list at the top of the page.
On the Resource Profile page, click Provision New Resource.
The Provision Resource to Organization page is displayed.
If you are using Oracle Identity Manager release 11.1.1, then:
On the organization details page, click the Resources tab.
From the Actions menu, select Provision. Alternatively, click Provision on the toolbar. The Provision Resource to Organization page is displayed in a new window.
On the Step 1: Select a Resource page, select one of the following options, and then click Continue:
Select the group option if you want to create a group.
The default settings to enable provisioning of Groups in organizational units in the AtMap.iPlanetGroup lookup definition are listed in the following table:
| Code Key | Decode |
|---|---|
|
Group Name |
cn |
|
nsuniqueid |
nsuniqueid |
Select the role option if you want to create a group.
The default settings to enable provisioning of Roles in organizational units in the AttrMap.iPlanetRole lookup definition are listed in the following table:
| Code Key | Decode |
|---|---|
|
Role Name |
cn |
|
nsuniqueid |
nsuniqueid |
On the Step 2: Verify Resource Selection page, verify the data that you provided, and then click Continue.
On the Step 5: Provide Process Data page, depending on whether you have selected a group or role while performing Step 4, enter the group or role details, and then click Continue.
On the Step 6: Verify Process Data page, verify the data that you have provided and then click Continue.
The "Provisioning has been initiated" message is displayed. Perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.3.x or release 9.1.0.x, click Back to User Resource Profile. The Resource Profile page shows that the group or role has been provisioned to the organization.
If you are using Oracle Identity Manager release 11.1.1, then:
Close the window displaying the "Provisioning has been initiated" message.
On the Resources tab, click Refresh to view the newly provisioned group or role.
Note:
This section describes an optional procedure. You need not perform this procedure if you do not want to enable provisioning of users in organizations.
In the AttrName.Prov.Map.iPlanet lookup definition, the following are default settings for enabling provisioning of users in organizational units:
ldapOrgDNPrefix=ou
ldapOrgUnitObjectClass=OrganizationalUnit
If you want to enable the provisioning of users in organizations, then change these settings as follows:
See Also:
Oracle Fusion Middleware User's Guide for Oracle Identity Managerfor detailed information about modifying lookup definitions
ldapOrgDNPrefix=o
ldapOrgUnitObjectClass=organization
Note:
It is assumed that you have performed the procedure described in Section 2.3.1.7, "Configuring Oracle Identity Manager for Request-Based Provisioning."
On Oracle Identity Manager release 11.1.1, if you want to switch from request-based provisioning to direct provisioning, then:
Log in to the Design Console.
Disable the Auto Save Form feature as follows:
Expand Process Management, and then double-click Process Definition.
Search for and open the iPlanet User process definition.
Deselect the Auto Save Form check box.
Click the Save icon.
If the Self Request Allowed feature is enabled, then:
Expand Resource Management, and then double-click Resource Objects.
Search for and open the iPlanet User resource object.
Deselect the Self Request Allowed check box.
Click the Save icon.
On Oracle Identity Manager release 11.1.1, if you want to switch from direct provisioning back to request-based provisioning, then:
Log in to the Design Console.
Enable the Auto Save Form feature as follows:
Expand Process Management, and then double-click Process Definition.
Search for and open the iPlanet User process definition.
Select the Auto Save Form check box.
Click the Save icon.
If you want to enable end users to raise requests for themselves, then:
Expand Resource Management, and then double-click Resource Objects.
Search for and open the iPlanet User resource object.
Select the Self Request Allowed check box.
Click the Save icon.