Hi, On Wednesday, 11. October 2006 19:31, Andrej Ricnik-Bay wrote: > On 10/12/06, Peter Marschall <[EMAIL PROTECTED]> wrote: > > Do you mean it fails to find entries that have the uid attribute set, > > but miss the cn attribute (or vice versa)? > > That is exactly the case. And it doesn't fail as in giving me an > error, it just silently doesn't return anything if one of the > attributes happens not to be defined. > > > It so, then it might be a problem with the data in the directory > > or the directory configuration. > > Well, there IS a problem. As I said - some users don't have a cn, > some don't have a uid, and as I found out yesterday, some don't > have either. (only six out of 8000).
Those who don't have either can be explained: they are not matched by the filter. > My other idea was the (since I have to query anonymously) that I > don't have permissions on some of those attributes for some of > the users; but even so, I still would have expected the OR to work. If the account you use for querying the directory does not hav the permissions to compare both cn & uid, then the OR will not work. It will not find those object that do only have the attribute set he is not allowed to compare. From the information you sent I can see no perl-ldap problem Peter -- Peter Marschall [EMAIL PROTECTED]
