Modifications in OUD are not Correctly Passed to OIM via LDAP User Create and Modify Recon (Incremental)

(Doc ID 2365007.1)

Last updated on JUNE 01, 2018

Applies to:

Identity Manager - Version 11.1.2.3.170718 and later
Information in this document applies to any platform.

Symptoms

Changes in OUD by ODSM are not being properly reconciled using LDAP User Create and Update Full Reconciliation.
It appears that updates are delayed, (2nd update causes 1st update to be reconciled)

Actually, for a Modify operation, the "delete" value of the attribute is reconciled instead of the "add" value
- ODSM does a 2 step replace when access OUD.

LDAPSync incremental does not parse the changelog properly and uses the "old" value instead of the "new" value.

EXAMPLE:
1. User changes the Mobile in OUD from 123-456-5555 to 123-456-1111.
The changelog entry "Changes" entry has the following format:
delete: mobilemobile: 123-456-5555-add: mobilemobile: 123-456-1111-replace: modifiersNamemodifiersName: cn=Directory Manager-replace: modifyTimestampmodifyTimestamp: 20180221193637Z-

OIM recon event shows the mobile value as 123-456-5555 and this is what is now in OIM.

2. If user does another change in OUD from 123-456-1111 to 123-456-3333
The changelog entry "Changes" entry has the following format:
delete: mobilemobile: 123-456-1111-add: mobilemobile: 123-456-3333-replace: modifiersNamemodifiersName: cn=Directory Manager-replace: modifyTimestampmodifyTimestamp: 20180221203637Z-

OIM recon event shows the mobile value as 123-456-1111 and this is what is now in OIM.
- Appears to be delayed, but actually parsed incorrectly.

All Full recons work and updates in OIM are pushed properly to OUD

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms