Identity Manager Drivers

This page is meant to provide a basic overview of how Identity Manager drivers work, what data goes over what channel and how to work with them. Because there are two main types of drivers I will discuss the eDir2eDir driver and the connected system driver, and then especially the AD driver.

This is the designer view of the eDir2eDir driver:
This is a schematic view of the eDir2eDir driver:

As you can see, data travels over both channels to get from the eDirectory Tree to the Vault and vice-versa.
From eDir-Tree to Vault First subscriber channel and then the publisher channel
From Vault to eDir-Tree First subscriber channel and then the publisher channel

As you can see, if data moves over a eDir2eDir driver, the data always goes from the subscriber channel to the publisher channel. This is important to remember in case you want to change the filters or policies, because they will have to be changed on both channels.

Here you can see the driver in more detail (also designer view):

This is the designer view of the AD connected system driver:
This is the schematic view of the AD connected system driver:

The connected system driver is far more simpler than the eDir2eDir driver. Data goes out of the Vault over the subscriber channel and into the Vault over the publisher channel.

Here you can see the driver in more detail (also designer view):