[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Empty search result
- To: Quanah Gibson-Mount <quanah@symas.com>, Fabiano Sidler <fabianosidler@swissonline.ch>, openldap-technical@openldap.org
- Subject: Re: Empty search result
- From: Howard Chu <hyc@symas.com>
- Date: Tue, 27 Nov 2018 17:11:07 +0000
- In-reply-to: <44E54EE8EE9B3DC771DE7E50@[192.168.1.39]>
- References: <20181127121015.vcssbzezdyntbzc4@fria.local> <44E54EE8EE9B3DC771DE7E50@[192.168.1.39]>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53
Quanah Gibson-Mount wrote:
> --On Tuesday, November 27, 2018 1:10 PM +0100 Fabiano Sidler <fabianosidler@swissonline.ch> wrote:
>
>> Hello!
>>
>> What can be the cause for ldapsearch without filter returning everything
>> as expected, but adding a filter (which works well against a 389 and an AD
>> installation) just returns nothing?
>> I can provide configs and logs if this is normal but unexpected (by me)
>> behaviour.
>
> You'd need to provide significantly more information than is available in the above text.
Most likely the filter uses matches that aren't defined in the schema. Servers
like 389 and AD are a lot more careless about schema details.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/