My tests were with openldap2.4.22.
(I have started to gradually migrate to current versions mainly due to IPv6 support in ACLs.)
On another server, where I still run v2.3.43-12.el5_5.3, the search works (without changing the schema):
# ldapsearch -x -v -D "cn=Manager,dc=noa,dc=gr" -W -s sub -b "ou=dns1,dc=noa,dc=gr" arecord=195.251.202.63 dn ldap_initialize( <DEFAULT> ) Enter LDAP Password: filter: arecord=195.251.202.63 requesting: dn # extended LDIF # # LDAPv3 # base <ou=dns1,dc=noa,dc=gr> with scope subtree # filter: arecord=195.251.202.63 # requesting: dn #
# nmilas1.astro, noa.gr, dns1, noa.gr dn: dc=nmilas1.astro,dc=noa.gr,ou=dns1,dc=noa,dc=gr
# search result search: 2 result: 0 Success
# numResponses: 2 # numEntries: 1
May that shed some light?
Nick
On 14/1/2011 2:10 μμ, Nick Milas wrote:
But why exact matches don't work with the attribute as it normally is in schema?