is the ACL in place (admin group comes before this acl with full read
to everything in the tree).
The last patch I sent you was not addressing this issue. In this case, I
believe the software is behaving as expected, according to the discussion
in <http://www.openldap.org/lists/openldap-devel/200701/msg00056.html>.
What the patch should give you, is the capability to compare the "member"
of the dynlist, assuming the identity you use has "compare" privs on the
attributes in the URL's filter. Would this be of help? In any case,
could you try it?