Fabrice Eudes wrote: > but, for the end user who doesn't know anything about LDAP directories, > this doesn't make sense; he might ask for the employeeType attribute > only (or anything else); then, if the filters isn't precise enough, like > objectClass=*, the entries -with no employeeType- attribute are badly > displayed. > No, this is not true.
If performing an (advanced) search with "show attributes": * empty: you should get each entry that matches your filter, showing the DN and all attributes of the entry (that your ldap ACLS let you see), * with "dn": you should get each entry that matches your filter, showing the just the DN * with "cn": you should get each entry that matches your filter, showing the DN and "cn" * with "cn,postaladdress" you should get each entry that matches your filter, showing the DN and "cn" and "postaladdress", etc The point is, the search will show the all entries that match your filter; the attributes that will show are the "rdn" AND the "dn" (even if you explicitly removed DN from the attribute list) AND any additional attributes you asked to see. Thus DN is shown whether you asked for it or not. Your output is not showing the "dn", thus entries that meet your filter and there are no attributes to show is resulting in badly formatted output - why isnt DN showing in your case? (Either PLA was modified, or your ldap acl's are stopping you from seeing it or another reason I havent thought of?) ...deon ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ phpldapadmin-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/phpldapadmin-users
