Enabling the Usage of UDFs in Requests

13-20 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager Transformation name=OneToOne Parameter name= employeeid fieldname= employeeid Transformation targetattr reconAttr e. Import the xml file back into MDS. After importing, verify that the full path in MDS is dbLDAPUser. f. Export the dbRA_LDAPUSER.xml file from MDS. g. Add the following entry to the end of the entity-attributes tag: attribute name=Employee ID typestringtype requiredfalserequired attribute-groupBasicattribute-group searchabletruesearchable attribute h. Add this entry to the end of the target-fields tag: field name= RECON_EMPLOYEE_ID typestringtype requiredfalserequired field i. Add the following entry to the end of the attribute-maps tag: attribute-map entity-attributeEmployee IDentity-attribute target-field RECON_EMPLOYEE_ID target-field attribute-map j. Import the RA_LDAPUSER.xml file back into MDS. After importing, verify that the full path in MDS is dbRA_LDAPUSER.xml.

13.5.2 Synchronizing UDFs Between Oracle Identity Manager and LDAP By Using the ldapsyncudf Utility

You can automate the synchronization of UDFs between Oracle Identity Manager and LDAP by using the ldapsyncudf.sh utility. This utility takes care of both provisioning and reconciliation of UDFs, and it is recommended that you synchronize UDFs by using this utility. If you want to provision UDFs without reconciliation, or if you want to reconcile UDFs without provisioning, then you must run the process manually as described in Synchronizing the Attribute Manually on page 13-18. Using the ldapsyncudf.sh script is described in the following sections: ■ Configuring the Properties File ■ Configuring the Input File ■ Running the Utility

13.5.2.1 Configuring the Properties File

You can configure properties in the ldapconfig.props file before running the ldapsyncudf.sh script to achieve UDF synchronization. These properties are used by the client to connect to the service provided by Oracle Identity Manager. These Configuring User Attributes 13-21 properties can also be specified through console if properties file does not exist or does not contain property values. You can configure the following properties: ■ OIMServer type: The application server type, such as Oracle WebLogic Server. If no value is specified, then Oracle WebLogic Server is the default value. ■ OIMProviderURL: Oracle Identity Manager provider URL. This is in the format t3:HOST_NAME:PORT. If the value is not specified in the properties file, then you are prompted to enter the value when running the ldapsyncudf.sh script. ■ OIMAdminUser: Oracle Identity Manager administrator user login. If the value is not specified in the properties file, then you are prompted to enter the value when you run the ldapsyncudf.sh script. ■ SkipOVDValidation: Whether or not LDAP attribute validation in OVD schema is skipped. By default the value is false. If the value of this property is true, then the LDAP attribute is not validated in OVD schema and it can be configured after running the utility. The utility makes the changes in MDS and horizontal tables. The following is a sample properties file: OIMServer Type, Valid values can be WLS, JBOSS, WAS OIMServerType=WLS OIMAdmin User Login OIMAdminUser=OIM_ADMINISTRATOR_LOGIN OIM Provider URL, such as OIMProviderURL=t3:HOST_NAME:PORT OIMProviderURL=t3:localhost:7001 Skip Validation of OVD Schema, such as SkipOVDValidation=true or false SkipOVDValidation=false

13.5.2.2 Configuring the Input File

The input to the utility can either be provided through an input file or at runtime in interactive mode as prompted through the console. If the input is provided though an input file, then it must be in the following format: ENTITY_TYPE, OPER_TYPE, UDF_NAME, LDAP_ATTR The input parameters are: ■ ENTITY_TYPE : The valid values can be either USER or ROLE. The values are not case-sensitive. ■ OPER_TYPE : The valid values can be either ADD or DELETE. The values are not case-sensitive. Note: The parameters must be separated by comma ,. Any line beginning with the hash character is treated as comment and is not processed by the utility.