6 Extending the Functionality of the Connector
You can extend the functionality of the connector to address your specific business requirements.
The following topics describe the procedures to extend the functionality of the connector :
6.1 Adding New Attributes for Reconciliation
The connector provides a default set of attribute mappings for reconciliation between Oracle Identity Governance and the target system. If required, you can add new user attributes for reconciliation using the user interface.
The default attribute mappings for reconciliation are listed in Attribute Mappings.
6.2 Adding New Attributes for Provisioning
The connector provides a default set of attribute mappings for provisioning between Oracle Identity Governance and the target system. If required, you can add new user attributes for provisioning using the user interface.
The default attribute mappings for provisioning are listed in Attribute Mappings.
Table 6-1 New Attributes and the Sample Values
| New Attributes | Sample Values |
|---|---|
| Phone | workAddress.phone |
| Postal Code | workAddress.postalCode |
Note:
The new attributes works on Update Account.6.3 Configuring Transformation and Validation of Data
Configure transformation and validation of user account data by writing Groovy script logic while creating your application.
You can configure transformation of reconciled single-valued user data according to your requirements. For example, you can use First Name and Last Name values to create a value for the Full Name field in Oracle Identity Governance.
Similarly, you can configure validation of reconciled and provisioned single-valued data according to your requirements. For example, you can validate data fetched from the First Name attribute to ensure that it does not contain the number sign (#). In addition, you can validate data entered in the First Name field on the process form so that the number sign (#) is not sent to the target system during provisioning operations.
To configure transformation or validation of user account data, you must write Groovy scripts while creating your application. For more information about writing Groovy script-based validation and transformation logic, see Validation and Transformation of Provisioning and Reconciliation Attributes of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.
6.4 Configuring Action Scripts
You can configure Action Scripts by writing your own Groovy scripts while creating your application.
You can configure Action Scripts by writing your own Groovy scripts while creating your application.
Configure these scripts to run before or after create, update, or delete an account provisioning operation. For example, you can configure a script to run before every user creation operation.
For information on adding or editing action scripts, see Updating the Provisioning Configuration in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.
6.5 Configuring the Connector for Multiple Tenants
You must clone the application of your base application to configure it for multiple tenants.
The following example illustrates this requirement:
XYZ corporation has multiple tenants including an independent schema. To meet the requirement posed by such a scenario, you must clone your application which copies all configurations of the base application into the cloned application.
For more information about cloning applications, see Cloning Applications in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.