Hi, I am having the issue detailed below where a change in driver A
causes a change to be picked up in driver B. I cannot use scoping to
stop this as the drivers necessarily apply to the same objects (I know
this sounds silly but there are reasons for it).
Does anyone have any suggestions for fixing this? Could I use the
Modifier field perhaps?
Thanks in advance
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> As always, traces. TID# 10098620. Also as Martyn said loopback
> ever happen on the engine side from one driver to itself. With that
> said if driver A makes a change in the engine and driver B picks it up
> and makes a new change at the engine, driver A can pick that up that
> event (wasn't from driver A at that point) and cause what appears to
> a loop. Traces will reveal this (look at the EventID of the events
> among other things).
> Good luck.
> email@example.com wrote:
> > IDM 3.0
> > Identity Vault - Netware 6.5 eDir 8.7.3
> > AD/Exchange 2003
> > Can anyone help with a question on AD loopback detection?
> > We are syncing from eDir to AD. Users are created fine in AD but we
> > get a corresponding event come down the Publisher channel which goes
> > a loop (going back down the Subscriber etc etc). For now I have
> > user sync on the Publisher channel but I want to place some rules in
> > to email the new starters and also to sync the email address back to
> > Vault.
> > Has anyone any simple solutions to allow these operations to take
> > whilst preventing the loop? I had thought of allowing the emails to
> > sent then perform a blanket veto but this will prevent the email
> > sync.
> > Any ideas? Thanks in advance.
> > Mark
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - 'mozdev.org - enigmail: index'
> iD8DBQFFpcYs7eGRNwWOK9IRAlzSAJ4n+7nvhaKABwv89Aoqwp omKnQfaQCePRcS
> -----END PGP SIGNATURE-----