DIP 11g/12c Directory Synchronization: CN (RDN) Attribute Value is Changed to Uppercase in Destination Active Directory
(Doc ID 2446575.1)
Last updated on NOVEMBER 30, 2022
Applies to:Oracle Internet Directory - Version 188.8.131.52.0 to 184.108.40.206.180621 [Release 11g to 12c]
Oracle Unified Directory - Version 220.127.116.11.0 to 18.104.22.168.180829 [Release 11g to 12c]
Information in this document applies to any platform.
The directory synchronization from Oracle Unified Directory (OUD) to Microsoft Active Directory (AD) has been configured.
The CN (RDN) attribute value in the destination AD entry is always lowercase even if the CN attribute value in the source OUD entry includes uppercase.
For example, the synchronization profile has the following attribute mapping:
cn:1: :inetorgperson:cn: :User:
cn:: :inetorgperson:givenname: :user:
This mapping means that the source CN attribute value goes into the destination CN and GIVENNAME attributes. The value is mapped without change because the mapping rule (arithmetic expression) is not defined.
The following entry is created in OUD. The CN attribute value includes uppercase.
Source OUD Entry:
cn: USER_01 <== Uppercase
The above OUD entry is synchronized to AD by DIP. Only CN attribute value becomes lowercase.
Destination AD Entry:
cn: user_01 <== Changed to Lowercase
givenName: USER_01 <== Kept Uppercase
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