4.1 Using Designer to Import

You can import the basic driver configuration file for the eDirectory driver by using Designer. This basic file creates and configures the objects and policies needed to make the driver work properly.

You can create a driver or import the eDirectory-IDM3_5_0-V1.xml configuration file onto an existing driver. The following procedure explains one of several ways to import the sample configuration file:

  1. Open a project in Designer.

  2. In the Modeler, right-click the Driver Set object, then select New > Driver.

  3. From the drop-down list, select eDirectory, then click Run.

  4. Configure the driver by filling in the fields.

    Specify information specific to your environment. For information on settings, see Table 4-1.

  5. After specifying parameters, click OK to import the driver.

  6. Customize and test the driver.

  7. Deploy the driver into the Identity Vault.

    See Deploying a Driver to an Identity Vault in the Designer 2.1 for Identity Manager 3.5.1 guide.

    Table 4-1 Settings for the eDirectory Driver

    Item

    Description

    Driver Name

    The object name to be assigned to this driver, or the existing driver for which you want to update the configuration.

    Remote Tree Address and Port

    Specify the DNS host name or IP address and port of the Identity Manager server in the remote tree. For example:

    151.155.144.23:8196

    hostname:8196

    C onfigure Data Flow

    Bidirectional: Both eDirectory™ trees are authoritative sources of the data synchronized between them.

    Authoritative: The local tree is the authoritative source.

    Subordinate: The local tree is not an authoritative source.

    Configuration Option

    Mirrored: Synchronizes objects hierarchically between the local and remote trees.

    If you choose this option, use the same option for configuring both eDirectory trees you are synchronizing.

    This option in the driver configuration synchronizes User, Group, Organization, Country, and Organizational Unit objects. It also mirrors the structure of a subtree in the other tree.

    Flat: Synchronizes all Users and Groups into specific containers.

    This option synchronizes User and Group objects and places all users in one container and all groups in another container.

    This option is typically used in conjunction with the Department option (or a similar configuration) in the other tree.

    This option doesn’t create the containers that hold the users and groups. You must create those manually.

    Department: Synchronize Users and Groups by department (OU).

    This option synchronizes User and Group objects and places all users and groups in a container based on the Department field in your management console.

    This configuration is typically used in conjunction with the Flat option (or a similar configuration) in the other tree.

    This option doesn’t create the containers for each department. You must create those manually. They must be the same as the container specified during import.

    Base Container

    Used for Mirrored, Flat, and Department options.

    Specify the base container for synchronization in the local tree, for example Users.MyOrganization.

    If using with Mirrored: The local base container to mirror with the Remote Base Container above.

    If using with Flat: The container to place Users into.

    If using with Department: The parent of the departmental containers.

    Password Sync Version

    Determines whether the driver synchronizes by using public/private keys (for DirXML 1.0) or the distribution password and password policies (for Identity Manager 2.1 or later).

    Password Failure Notification User

    Specifies which user receives e-mail notifications when password updates fail.

    Remote Base Container

    Used for Mirrored option only.

    Specify the base container for synchronization in the remote tree, for example Users.MyOrganization.

    Group Container

    Used for Flat only.

    Specify the base container for synchronization in the local tree to place Groups into, for example Groups.MyOrganization.