You create the eDirectory driver by importing the driver’s basic configuration file and then modifying the configuration to suit your environment. After you’ve created and configured the driver, you need to deploy it to the Identity Vault and start it. To connect two trees, you need to do this for the driver installed in each tree.
In Designer, open your project.
In the Modeler, right-click the driver set where you want to create the driver, then select
> to display the Driver Configuration Wizard.In the Driver Configuration list, select
, then click .On the Import Information Requested page, fill in the following fields:
Driver Name: Specify a name that is unique within the driver set.
Remote Tree Base Container: Specify the source container for the eDirectory objects.
User Container: Select the Identity Vault container where any new users created from eDirectory file information will be placed. This value becomes the default for all drivers in the driver set. If you don’t want to change this value for all drivers, leave this field alone and change the value on the driver’s Global Configuration Values page after you’ve finished importing the driver.
Group Container: Select the Identity Vault container where any new groups created from eDirectory file information will be placed. This value becomes the default for all drivers in the driver set. If you don’t want to change this value for all drivers, leave this field alone and change the value on the driver’s Global Configuration Values page after you’ve finished importing the driver.
Remote Tree Address and Port: Specify the host name or IP address, and communication port of the Identity Manager server in the remote tree.
Click
to import the driver configuration.At this point, the driver is created from the basic configuration file. To ensure that the driver works the way you want it to for your environment, you must review and modify the driver’s default configuration settings.
To review or modify the default configuration settings, click Configuring the Driver.
, then continue withor
To skip the configuration settings at this time, click Configuring the Driver.
. When you are ready to configure the settings, continue withAfter importing the driver configuration file, the eDirectory driver will run. However, the basic configuration might not meet the requirements for your environment. You should complete the following tasks to configure the driver:
Secure the driver connection: eDirectory drivers communicate via SSL using digital certificates for authentication. You need to set up this secure connection. See Section 5.0, Securing Driver Communication.
Configure the driver filter: Modify the driver filter to include the object classes and attributes you want synchronized between the two eDirectory trees. For information about the classes and attributes include in the filter for the basic configuration, see Section B.0, Synchronized Attributes.
Configure policies: Modify the policies as needed. Policies should generally be placed only on the Publisher channel, not on the Subscriber channel. The Matching and Placement policies cannot operate correctly on the Subscriber channel because the Subscriber channel is acting primarily as a source of events for the Publisher channel of the other tree.
You might consider placing an Event Transform or Create Policy on the Subscriber channel to prevent sending unnecessary data across the channel. See Using Scope Filtering to Manage Users on Different Servers
in the Identity Manager 3.6.1 Installation Guide.
Configure password synchronization: The basic driver configuration is set up to support bidirectional password synchronization through Universal Password. If you don’t want this setup, see Section 6.0, Synchronizing Passwords.
After completing the configuration tasks, continue with the next section, Deploying the Driver.
After a driver is created in Designer, it must be deployed into the Identity Vault.
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
.If you are authenticated to the Identity Vault, skip to Step 5, otherwise, specify the following information:
Host: Specify the IP address or DNS name of the server hosting the Identity Vault.
Username: Specify the DN of the user object used to authenticate to the Identity Vault.
Password: Specify the user’s password.
Click
.Read through the deployment summary, then click
.Read the successful message, then click
.Click
to assign rights to the driver.The driver requires rights to objects within the Identity Vault. The Admin user object is most often used to supply these rights. However, you might want to create a DriversUser (for example) and assign security equivalence to that user. Whatever rights that the driver needs to have on the server, the DriversUser object must have the same security rights.
Click
, then browse to and select the object with the correct rights.Click
twice.Click
to exclude users that should not be synchronized.You should exclude any administrative User objects (for example, Admin and DriversUser) from synchronization.
Click
.When a driver is created, it is stopped by default. To make the driver work, you must start the driver and cause events to occur. Identity Manager is an event-driven system, so after the driver is started, it won’t do anything until an event occurs.
To start the driver:
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
.For information about management tasks with the driver, see Section 7.0, Managing the Driver.