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.
Greetings, Fabiano
--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.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
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.
openldap-technical@openldap.org
-
Fabiano Sidler -
Howard Chu -
Quanah Gibson-Mount