Hello all:

We have a JDBC driver(1.6.4) which connects with eDirectory ( and
Oracle (8.1.7). In the subscriber output transformation, we have a policy
to set the modifier to the same ID as "Authentication ID" in the driver
configuration. We thought this would prevent the driver pick up the change
that done by the subscriber channel. For our testing, we bulkloaded all
the users using ice into eDirectory. Subscriber found the match and
updated the information in Oracle for the user. However the published
channel then tried to send the new value to eDirectory. I would like to
know why the loopback prevention failed. Is it because we loaded all the
data using ice? Thank you

Jie Feng