[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (?=undefined)



--On Wednesday, April 05, 2006 9:06 AM +0200 Uwe Hering <hering_uwe@web.de> wrote:

Hello,

recently I switched from 2.1.4 to 2.3.19.

Everything works fine as expected, only one application raised a problem:

using the application the following search filter arrived on 2.1.4 in the
log  correctly:

"(&(objectClass=XXXPerson)(givenName=*)(sn=Schmi*)(ou=*)(telephoneNumber=
*))"

now on 2.3.19 the following message occurs using the same conditions on
app  side:

"(&(objectClass=XXXperson)(?=undefined)(sn=Schmi*)(?=undefined)(?=undefin
ed))"

If one enters substrings in _all_ filter attributes (givenName, sn,
telephoneNumber) everything is ok again.

I would guess there is something else wrong with what you are doing. For example, I run the following query with my OL 2.3.20 server:

ldapsearch -LLL -Q -h ldap-test3 "(&(objectClass=superson)(givenName=*)(sn=moun*)(ou=*)(telephoneNumber=*))"


and I get in the logs:


Apr 5 13:32:16 ldap-test3.Stanford.EDU slapd[22344]: [ID 469902 local4.debug] conn=623 op=4 SRCH base="dc=stanford,dc=edu" scope=2 deref=0 filter="(&(objectClass=suPerson)(givenName=*)(sn=moun*)(ou=*)(telephoneNumber=*))"


My best guess is that you have not loaded the schema into your ldap server defining the attributes that are coming back as undefined (and hence, they are undefined).

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html