You set defaults for policies and filters when you import the driver configuration. If you want to change the default behavior of the driver, we recommend that you make modifications in this order:
Modify the driver filter to include additional attributes to be synchronized. See Modifying the Driver Filter for more information.
Modify the Schema Mapping policy to include all attributes to be synchronized. See Adding Entries to the Schema Mapping Policy for more information.
Modify the Subscriber Create policy. See Modifying the Create Policy for more information.
Modify the Subscriber Placement policy. See Modifying Policies.
The driver filter contains the Identity Vault classes and attributes for the Publisher and Subscriber channels. The purpose of the filter is to define how attributes are shared between systems. All attributes in the driver filter are required for processing, so you should not remove attributes from the filter.
You can, however, make additions to the filter. If you add classes or attributes to the filter, you must append the merge-authority=“edir” string to the added attribute in the Mapping policy.
For example:
<filter-attr attr-name=“Description” merge-authority=“edir” publisher=“ignore” subscriber=“sync”/>
The Schema Mapping policy is contained in the driver object and applies to both the Subscriber and Publisher channel. The purpose of the Schema Mapping policy is to map schema names (particularly attribute names and class names) between the Identity Vault namespace and the GroupWise namespace. Do not modify or remove existing entries in the Schema Mapping policy. You can, however, add entries to the Schema Mapping policy.
You modify the Create policy to implement your specific business rules. The Create policy determines whether or not a GroupWise account is created. A Create policy also can perform other modifications to the Add event, such as providing default values for attributes.
In the driver configuration, the Create policy specifies two required attributes: CN and Surname.
The policy is controlled by a global configuration value (GCV) that sets the initial password to Surname and CN. For more information on GCVs, refer to Section A.2, Global Configuration Values.
Matching policies define the minimum criteria that two objects must meet to be considered the same. We recommend that you do not change the default Matching policy.