We can't search expected entries from LDAP server

Solution Verified - Updated -

Issue

  • Our customer defines "exg<Name>" attribute in the entries on his LDAP server. In addition, he uses "index" for "exg<Name>" attribute.
    slapd.conf
    ----------------------------
     index exg<Name> eq
    ----------------------------

    /var/lib/ldap/
    -----------------------
     exg<Name>.bdb
    -----------------------
  • We add the same entries both on RHEL5.x(openldap-2.3.x) and on RHEL6.5(openldap-2.4.43) by LDIF file and we search entries with following search formula.
    *The minimum value of "exg<Name>" attribute's value is "19000101", and the maximum value of it is "20150121".

    # slapadd -f /etc/openldap/slapd.conf -l slapcat.log
    
    # ldapsearch -x -H ldap://127.0.0.1 -b 'ou=Users,ou=usermtn,dc=*******,dc=local' -D cn=Manager,dc=*******,dc=local -w ********* -LLL -s one '(exg<Name><=20150130)'
    
  • We can search intended numbers of entries (38034) on openldap-2.3.x, on the other hand, in the case of openldap-2.4.43, the search result is 33115. Moreover, we delete index of "exg<Name>" attribute and re-search entries, we can search intended numbers of entries (38034) on openldap-2.4.43.

    Snipped from slapd.conf
    -----------------------------
     #index exg<Name> eq
    -----------------------------

    # rm /var/lib/ldap/exg<Name>.bdb

Environment

  • Red Hat Enterprise Linux 6 Update 5
  • Architecture: x86_64
  • Package Version: openldap-2.4.23-32.el6_4.1.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content