OUD 12c Complex "ldapsearch" Command Filter Does Not Work as Expected After Migration from ODSEE to OUD
(Doc ID 2374065.1)
Last updated on MAY 01, 2023
Applies to:
Oracle Unified Directory - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
After a transformation from ODSEE to OUD an issue with complex ldap search filters is encountered.
Complex ldapsearch filter fails to return any results. The same search, however provides results in ODSEE .
ldapsearch -h 0.0.0.0 -p <PORT> -D "cn=<DS_ADMIN>" -X -j <PASSWORD_FILE> -b "<SUFFIX_DN>" "(&(entrydn=cn=*,ou=groups,o=*,<SUFFIX_DN>)(uniqueMember=cn=*,cn=ABC1,ou=applications,o=*,<SUFFIX_DN>)(uniqueMember=uid=<UID>*,ou=users,o=*,<SUFFIX_DN>))"
Changes
The current environment is OUD 12.2.1.3.0 + patch 26397668
The Patch 26397668: OUD SEARCH BEHAVIOR WITH WHITESPACE AND WILDCARD (*) IN THE SEARCH FILTER for Oracle Unified Directory 12.2.1.3.0 has been released in order to fix the issue, but it didn't.
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 |