OUD - When using the "ldapsearch" Command Requested Attributes are not Returned in the Same Sequence as Requested
(Doc ID 2607921.1)
Last updated on MARCH 11, 2024
Applies to:
Oracle Unified Directory - Version 12.2.1.3 and laterInformation in this document applies to any platform.
Symptoms
Customer Issue:
============
Data is imported from Oracle Directory Server Enterprise Edition (ODSEE) to Oracle Unified Directory (OUD). The issue is that when using ldapsearch against OUD, the attributes are not returned in the same sequence they are being requested.
For example:
In ODSEE:
------------
./ldapsearch -h <ODSEE HOST> -p PORT> -D "cn=" -w - -b "dc=<SUFFIX_DN>" uid= dn sn cn givenname mail
Password for user 'cn=':
dn: uid=,<User Base DN>
sn: <SN>
cn: <CN1>
cn: <CN2>
givenname: <GN>
mail: <email>
In OUD :
---------
./ldapsearch -h <OUD HOST> -p <OUD PORT> -D "<Directory Manager user>" -w - -b "dc=<SUFFIX_DN>" uid= dn sn cn givenname mail
Password for user 'cn=':
dn: uid=,<User Base DN>
mail: <email>
givenname: <GN>
sn: <SN>
cn: <CN1>
cn: <CN2>
When checking with ldapsearch command in ODSEE the attributes requested (sn, cn, givenname and mail) are returned in the same order as requested in the output. When performing the same search in OUD, the order returned is different.
Changes
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 |