it looks like a problem to me, but I might be wrong. It seems
that Net::LDAP::FilterMatch doesn't cope with filters of the type:

(dn=*)
(dn=cn=joe doe,ou=somewhere)

but it does work neatly if I write them like this:

(distinguishedName=*)
(distinguishedName=cn=joe doe,ou=somewhere)

I have a test case showing this, here:

https://github.com/russoz/perltests/tree/master/test-net-ldap-filterm...

Am I missing something here?

Best
PEter

One possible explatation might be:
If you have the name of the object, you can make a more efficient query:

        $ldap->search(base => $YOUR_KNOWN_DN,
                                filter => '(objectclass=*)',
                                scope => base);

I.e. you set the search base to your known DN, set the scope to 'base',
(i.e. only the object given as base) and query for all objects.
This gives you the most efficient query if you already know a DN.

=> Using the DN alone on the left hand side of a filter is simply not
necessary.

Chris,
I am fully aware of DN as part of the left hand side in extensible matches.
But in those cases the filter searches for specific values of RDNs as parts of
the DN, not the full DN.

Best
Peter