Deleted Users In AD Are Not Synchronized By DIP TO ODSEE
(Doc ID 2909479.1)
Last updated on NOVEMBER 28, 2022
Applies to:
Oracle Internet Directory - Version 11.1.1.9.0 and laterInformation in this document applies to any platform.
Symptoms
Customer have ODSEE - AD bidirectional synchronization. Synchronizing users, create, modify is working fine.
When we delete a user in AD, synchronization fail, user is not deleted from ODSEE.
There is in ODSEE logs:
[17/Aug/2022:17:01:52 +0200] conn=2428535 op=1 msgId=2 - SRCH base="[CONTAINER_DN]" scope=2 filter="(orclObjectGuid=OW3XhAwc5Uq372yvnVLwxw==)" attrs=ALL(null)
authzid="dn:orclodipagentname=ADtoDS,cn=subscriber profile,cn=changelog subscriber,cn=directory integration platform,cn=products,cn=OracleContext"
..
[17/Aug/2022:17:01:52 +0200] conn=2428535 op=1 msgId=2 - RESULT err=11 tag=101 nentries=0 etime=0 notes=U
authzid="dn:orclodipagentname=ADtoDS,cn=subscriber profile,cn=changelog subscriber,cn=directory integration platform,cn=products,cn=OracleContext"
..
[17/Aug/2022:17:01:52 +0200] conn=2428535 op=1 msgId=2 - RESULT err=11 tag=101 nentries=0 etime=0 notes=U
Changes
Configure ODSEE - AD synchronization using DIP. Try to delete user from AD.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |