My Oracle Support Banner

Different Search Behavior With IntegerMatch Matching Rule Between OUD and ODSEE (Doc ID 1922820.1)

Last updated on FEBRUARY 04, 2019

Applies to:

Oracle Unified Directory - Version 11.1.2.2.0 and later
Oracle Directory Server Enterprise Edition - Version 6.0 and later
Information in this document applies to any platform.

Goal

Different search behavior with IntegerMatch matching rule between OUD and ODSEE in the following specific case -

 

For instance, for the following entry.

dn: cn=posixGroup1,ou=Groups,dc=example,dc=com
cn: posixGroup1
gidNumber: 1
objectClass: groupofuniquenames
objectClass: posixGroup
objectClass: top


In ODSEE, search with filter gidNumber="1 1" returns the above entry -

# ldapsearch -p 1111 -D "cn=directory manager" -w <PASSWORD> -b dc=example,dc=com gidnumber="1 1"
version: 1
dn: cn=posixGroup1,ou=Groups,dc=example,dc=com
objectClass: posixGroup
objectClass: top
cn: posixGroup1
gidNumber: 1
#



On the other hand, OUD doesn't return the entry for this search when using the same search filter -

-bash-3.2$ ldapsearch -p 9999 -D "cn=Directory manager" -w <PASSWORD> -b dc=example,dc=com gidnumber="1 1"
-bash-3.2$ ldapsearch -p 9999 -D "cn=Directory manager" -w <PASSWORD> -b dc=example,dc=com gidnumber="1"
dn: cn=posixGroup1,ou=Groups,dc=example,dc=com
cn: posixGroup1
gidNumber: 1
objectClass: groupofuniquenames
objectClass: posixGroup
objectClass: top

-bash-3.2$



Is the OUD behavior correct ?

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.