SHIFT

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


Sidebar

Sponsor:

Would you like to sponsor this site?
Or buy me a beer?:


Recently Changed Pages:

View All Pages
View All Q Pages


View All Tags


Sign up for Q to post comments.





WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.


Terms And Conditions for Q users


Pages with comments

PageDateDiscussionTags
2019/06/22 10:36 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments

idmdrivers

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.

eDir2eDir driver

This is the designer view of the eDir2eDir driver:
idmdriver01.jpg
This is a schematic view of the eDir2eDir driver:
idmdriver02.jpg

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):
idmdriver05.jpgidmdriver06.jpg

Connected System driver

This is the designer view of the AD connected system driver:
idmdriver03.jpg
This is the schematic view of the AD connected system driver:
idmdriver04.jpg

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):
idmdriver07.jpg

You could leave a comment if you were logged in.
idmdrivers.txt · Last modified: 2013/04/21 20:46 by sjoerd