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 column 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.
For data that fails the validation check, the following message is displayed or recorded in the log file:
oracle.iam.connectors.icfcommon.recon.SearchReconTask : handle : Recon event skipped, validation failed [Validation failed for attribute: [FIELD_NAME]]
Note:
This feature cannot be applied to the Locked/Unlocked status attribute of the target system.
To configure validation of data:
- Write code that implements the required validation logic in a Java class.
The following sample validation class checks if the value in the First Name attribute contains the number sign (#):
package com.validate;
import java.util.*;
public class MyValidation {
public boolean validate(HashMap hmUserDetails,
HashMap hmEntitlementDetails, String field) {
/*
* You must write code to validate attributes. Parent
* data values can be fetched by using hmUserDetails.get(field)
* For child data values, loop through the
* ArrayList/Vector fetched by hmEntitlementDetails.get("Child Table")
* Depending on the outcome of the validation operation,
* the code must return true or false.
*/
/*
* In this sample code, the value "false" is returned if the field
* contains the number sign (#). Otherwise, the value "true" is
* returned.
*/
boolean valid=true;
String sFirstName=(String) hmUserDetails.get(field);
for(int i=0;i<sFirstName.length();i++){
if (sFirstName.charAt(i) == '#'){
valid=false;
break;
}
}
return valid;
}
}
- Create a JAR file to hold the Java class.
- Run the Oracle Identity Manager Upload JARs utility to post the JAR file to the Oracle Identity Manager database. This utility is copied into the following location when you install Oracle Identity Manager:
Note:
Before you use this utility, verify that the WL_HOME environment variable is set to the directory in which Oracle WebLogic Server is installed.
When you run the utility, you are prompted to enter the login credentials of the Oracle Identity Manager administrator, URL of the Oracle Identity Manager host computer, context factory value, type of JAR file being uploaded, and the location from which the JAR file is to be uploaded. Specify 1 as the value of the JAR type.
See Also:
Upload JAR Utility in
Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
- If you created the Java class for validating a process form field for reconciliation, then:
- Log in to the Design Console.
- Expand Administration, and then double-click Lookup Definition.
- In the Code field, enter Lookup.RESOURCE.UM.ReconValidation as the name of the lookup definition.
- Select the Lookup Type option.
- On the Lookup Code Information tab, click Add.
A new row is added.
- In the Code Key column, enter the resource object field name. For example, First Name.
- In the Decode column, enter the class name. For example, com.validate.MyValidation.
- Save the changes to the lookup definition.
- Search for and open the Lookup.RESOURCE.UM.Configuration lookup definition.
- Create an entry with the following values:
Code Key: Recon Validation Lookup
Decode: Lookup.RESOURCE.UM.ReconValidation
- Save the changes to the lookup definition.
- If you created the Java class for validating a process form field for provisioning, then:
- Log in to the Design Console.
- Expand Administration, and then double-click Lookup Definition.
- In the Code field, enter Lookup.RESOURCE.UM.ProvValidation as the name of the lookup definition.
- Select the Lookup Type option.
- On the Lookup Code Information tab, click Add.
A new row is added.
- In the Code Key column, enter the process form field name. In the Decode column, enter the class name.
- Save the changes to the lookup definition.
- Search for and open the Lookup.RESOURCE.UM.Configuration lookup definition.
- Create an entry with the following values:
Code Key: Provisioning Validation Lookup
Decode: Lookup.RESOURCE.UM.ProvValidation
- Save the changes to the lookup definition.