Hello, Yes, once I realized that the "cn=users" had 3 group objects in them, then the count make sense. So there were like 5,386 (in parenthesis), but the export was 5,385. As an example. What does puzzle me, though, is why does Apache have the number in parenthesis be different than the search results? I thought they should match.
Example: Let's say you have ou=users And you have 500 user objects in there. 100 of the users have mail attribute present. The other 400 do not. I would've thought that if you construct an LDAP query of base: ou=users and something like: (&(objectclass=user)(mail=*)) That the number in parenthesis would be 100, and the results would be 100. In this case, for some strange reason, Apache feels the need to include the 3 group objects in the parenthesis even though the search filter doesn't count/include them. I don't recall seeing this behavior before in any directory/query I've done (ie: the number in parenthesis seems to always equal the actual results displayed, etc.) ?? -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Wednesday, February 25, 2015 4:56 PM To: [email protected] Subject: Re: Apache Directory Studio-incorrect counts via LDAP Le 25/02/15 20:39, Hurni, Kevin (ITS) a écrit : > There is no subtree as previously stated in the cn=users area in the AD tree. > > Unless I'm misinterpreting the use of the word subtree. Ah, sorry, my bad. I misinterpreted the groups you are talking about, thinking they were sub-entries. So basically, the count you get is equal to what you have, right ?
