Your connection string is probably wrong try something like this The end result with this policy on the Publisher, is that the identity vault is the authoritative source for the email attribute. Be sure to test in a non-production environment. The Loopback driver will allow us to do this on the fly. Be sure to test in a non-production environment.

Uploader: Zulkijora
Date Added: 5 July 2017
File Size: 17.12 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 54710
Price: Free* [*Free Regsitration Required]

Create a driver set on a server, or a new driver in a driver set.

Cool Solutions: Setting Up a Loopback Driver with a Group Entitlement for eDirectory

This is only Example code. Page 1 of 2 1 2 Last Jump to page: The engine runs on the Java Virtual Machine loopbaxk eDirectory. For the loopback driver to function properly, it is best to have all processing happen on the Subscriber Channel.

On Termination, disable user and move to Disabled container This policy contains a loopbac rule which disables a user’s account and moves them to a disabled container when the Description attribute indicates they are terminated.

These reasons immediately come to mind: More specifically, have all processing happen in the Event Transformation of the Subscriber Channel.

The answer to those questions are, whatever you want and however you want. ODBC Driver Manager] Data source name not found and no default driver loopbacm Im rewriting an old asp page that still works fine that connects to an access database using a system dsn.

Also the managerworkforceID should be automatically added to userA based on the dn of the userB the assigned manager And the same process looopback removing the manager attribute of userA.


Loopback Driver & Code(-9024) Unable to read current state of .

Or, what are other good examples of on-the-fly modifications do you need, to match your environment? You could have the Subscriber channel of the Work Order driver event on changes in the vault, and make the DirXML-WorkOrder objects itself, when the conditions are right.

We have found this forum to be extremely helpful with the day-to-day work of dealing with Novell’s IDM product. The error was received because the Set Destination Attribute was used in policy.

The layout for this driver is something like this: You can view the vault as a private data store for Identity Manager that holds enterprise-wide data.

This is when a successfully processed Work Order would normally be deleted. After all processing is completed veto everything so nothing syncronizes to the “Application”.

For those still stuck in XSL: This is probably what confuses the heck out of people. This was used so that if an object was moved, the other driver doing the move could set this flag, which would trigger the Loopback driver to do its magic after the move.

Setting Up a Loopback Driver with a Group Entitlement for eDirectory

Here’s the main reason this is of interest to my group. Which is a completely different change that shipped in an earlier IDM release. Can I have the solution to this Error? When you see the manager attribute looback, you just need to perform a set destination attribute. It was fixed in 4.


This will not cause the driver to event on the WorkOrder creation, since the driver itself created it and loopback protection will prevent that from happening. The remaining actions output the trace message and generate an audit event using the local variables in the first rule. There are some good articles to consider reading as you contemplate using a Work Order driver, which you can find at these links: Originally Posted by geoffc.

The offset can be specified as any integer number of one of the following:. NetIQ Identity Manager is a service that synchronizes data among servers in a set of connected systems by using a robust set of configurable policies.

Of course, the src-dn of the Work To Do will be the DN of the Work Order itself, so you can always go back and read the destination attribute when in the Publisher channel from the Work Order itself and add it into the Work To Do creation if diirxml need more information. Also, the use of the DestQueryProcessor was used in policy.

You will probably want to add a User and object class. What other neat things can you think of to do with this driver?