Synchronizing the Attribute Manually

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. 13-22 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager ■ UDF_NAME : The valid values can be any Oracle Identity Manager entity attribute, which has been created successfully. If the UDF_NAME does not exist, then an error message is displayed. The value is case-sensitive. ■ LDAP_ATTR : The valid values can be any LDAP attribute present in the LDAP directory server as well as in the OVD schema. The LDAP_ATTR parameter is optional for the DELETE operation. If this parameter value is specified for the DELETE operation, then this attribute value is ignored. The value is case-sensitive. The following is a sample input file: USER, ADD, udf1, ldapAttr1 ROLE, ADD, udf2, ldapAttr2 ROLE, DELETE, udf3 This is comment USER, DELETE, udf4 USER, ADD, UDF Number 5, ldapAttr5

13.5.2.3 Running the Utility

The ldapsyncudf.sh script is in the ORACLE_HOMEserverldap_config_util directory. To run the ldapsyncudf.sh script: 1. Extend the OVD and OID schemas by adding the LDAP attribute, such as employeeid, to the orclIDXPerson objectclass in both OVD and OID. 2. Before running the utility, set the WL_HOME and JAVA_HOME environment variables. 3. Run the following command: ldapsyncudf.sh [-Dconfig.properties=PATH_TO_PROPERTIES_FILE] [-DinputFile=PATH_TO_INPUT_FILE] You can run the utility in any one of the following ways: ■ Both the command-line parameters are optional. If the command-line parameters are not specified, then you are prompted to enter the parameters at runtime through the console, as shown: Enter Entity Type User Role: Specify the Oracle Identity Manager entity type, which is USER or ROLE. Enter Operation Type Add Delete: Specify the operation type, which is ADD or DELETE. Tip: Update is not supported. To perform an update, first perform delete followed by add. A new definition is picked from Oracle Identity Manager entity definition file present in the MDS. Note: Before running the utility, create the LDAP attribute and include that in the orclIDXPerson or orclIDXGroup objectclass as depending on the entity type. Tip: Run the ldapsyncudf.sh script with help, –help, or --help command-line parameter to display usage details and general help. Configuring User Attributes 13-23 Enter OIM UDF Name to be Synchronized: Specify the Oracle Identity Manager entity attribute which has been created successfully. Enter the LDAP attribute name in LDAP schema: Specify the LDAP attribute present in the LDAP directory server as well as in the OVD schema. This is an optional parameter for the DELETE operation. One set of operation is completed. If the operation is successful, then you are prompted, as shown: Want to continue adding deleting more attributes yn? Enter y if you want to start the input process for another operation. Otherwise, enter n to end the program. ■ Run the utility with values for the -Dinputfile and -Dconfig.properties command-line parameters. The input is read from the input file. The input file can contain multiple inputs, one per line. Each input contains four parameters for ADD operation or three parameters for DELETE operation. If you provide the fourth parameter for a DELETE operation, then it is ignored.

13.6 Configuration Management Architecture

For all attribute definitions and the Configuration Management pages in the UI, the configuration file for maintaining the user entity attributes is User.xml. This configuration file defines all attributes of user entity and their properties. The mapping of the attribute to the backend attributes or columns is also specified in the file. The attributes to be displayed on the UI are determined based on the attribute properties. For example, if an attribute is system-controlled, then the attribute is not displayed in the UI. Example 13 1 shows the code for a sample User.xml configuration file: Example 13 1 The User.xml Configuration File ?xml version=1.0 encoding=UTF-8? tns:entity-definition xmlns:tns=http:www.oracle.comschemaoimentity xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:www.oracle.comschemaoimentity ..entity.xsd entity-type child-entity=falseUserentity-type -- Defines the repository and data provider to use for this entity -- provider-instance repository-instanceOperationalDBrepository-instance provider-typeUserDataProviderprovider-type parameters parameter name=table valueusrvalue parameter parameter name=id_column valueusr_keyvalue parameter parameter name=usr_foreign_key_column valueusr_manager_keyvalue parameter parameter name=org_table valueactvalue parameter