I have an LDAP driver that connects eDiretory with an LDAP directory (in
this case is IBM Directory Server) unidirectional from eDir to IBM
I'm using IDM 3.0.1 and eDir 184.108.40.206 on SLES 10.
I'm matching users only by the "CN" attribute in a hierarchical to flat
In a first scenario, a user exists in the IBM Directory that is not
associated with one in eDir. In this case the matching policy works ok,
and matches and associates a new user in eDir with the same CN that the
one in IBM.
In a second scenario, a user exists in the IBM Directory that is already
associated with a user in eDirectory. When I create a new user in
eDirectory (with the same CN that the one associated in IBM) the
matching policy tries to find a match, which it does, but because its
already associated with another user in eDirectory, the matching policy
realizes what is happening and stops the current operation with an error
(-9063 - Found user that is already associated with another object).
OK so far, but the thing is that I want to handle that error, but no
status operation is sent by matching policy on the suscriber channel. It
just simply stops.
Does anyone now how to handle that event?? (I've been looking in forums,
novell support, etc, but I didn't find any useful information, I've also
looked at this page:
http://developer.novell.com/document...ng-object.html , but when I follow the driver LOGS, both matching events (first and second scenarios) looks exactly the same, so I can't tell the difference between a matched object that is not associated with one that it is. But somehow Matching policy realizes that and stops the operation)
Thanks in advance,