Active Directory Entry Not Synchronized If a Mapped Attribute Contains a Blank Space (Doc ID 1105593.1)

Last updated on JULY 01, 2016

Applies to:

Oracle Internet Directory - Version 10.1.2.3 and later
Information in this document applies to any platform.

Symptoms

Active Directory Synchronization to OID is configured.
Changes for Active Directory entries are not synchronized, if the Active Directory entry contains a blank space for an attribute value ,this attribute is configured in the Attribute Mapping Rules and the associated OID entry does not contain a value for the mapped attribute.

The blank space prevents the entry to be synchronized even if other mapped attributes are changed.
The DIP Synchronization log file does not show an error, but reports a successful synchronization.

Changes for other Active Directory Entries are synchronized successful.


 

Example:

Attribute mapping rules:
title: : :user:title: :organizationalPerson:
mobile: : :organizationalperson:mobile: :inetorgperson:

AD User entry contains attribute values:
title: " a blank space, not empty "
mobile: 123456

OID entry contains:
mobile: 123456

In this scenario changes in AD for the attribute "mobile" would not be synchronized to OID, because the "title" attribute contains a blank space.



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