LDAP auth problem - old or new bug, or user error?

[lois]

hello all -

I have TestLink 1.8 up and running. I hit a few snags during installation, but everything was surmountable without too much trouble... until i tried to set up LDAP authentication. Fail.

I have the following in my config.inc.php:

$tlCfg->authentication['method'] = 'LDAP';

/** LDAP authentication credentials */
//$tlCfg->authentication['ldap_server'] = "ldap://ldap.rockyou-internal.com";
//$tlCfg->authentication['ldap_port'] = '389';
//$tlCfg->authentication['ldap_version'] = '3'; // could be '2' or '3' in some cases
//$tlCfg->authentication['ldap_root_dn'] = "ou=people,dc=rockyou-internal,dc=com";
//$tlCfg->authentication['ldap_organization'] = ''; // e.g. '(organizationname=*Traffic)'
//$tlCfg->authentication['ldap_uid_field'] = 'uid'; // Use 'sAMAccountName' for Active Directory
//$tlCfg->authentication['ldap_bind_dn'] = ''; // Left empty for anonymous LDAP binding
//$tlCfg->authentication['ldap_bind_passwd'] = ''; // Left empty for anonymous LDAP binding

I have LDAP errors as follows in the userlog0.log (extended level logging):

ldap_search() [<a href='function.ldap-search'>function.ldap-search</a>]: Search: No such object - in /var/www/vhosts/testlink.rockyou-internal.com/httpdocs/testli
[10/Aug/20 20:38:29][WARNING][<nosession>][GUI]
E_WARNING
ldap_get_entries(): supplied argument is not a valid ldap result resource - in /var/www/vhosts/testlink.rockyou-internal.com/httpdocs/testlink/lib/functions/ldap_
[10/Aug/20 20:38:29][WARNING][<nosession>][GUI]
E_WARNING
ldap_free_result(): supplied argument is not a valid ldap result resource - in /var/www/vhosts/testlink.rockyou-internal.com/httpdocs/testlink/lib/functions/ldap_
[10/Aug/20 20:38:29][AUDIT][<nosession>][GUI]

Network tools show the testlink server making a connection to the LDAP server, and the two servers exchanging their ACKs. Logs on the LDAP server show a connection. But, users trying to login with LDAP are repeatedly unsuccessful.

I noticed some LDAP bugs have been fixed in past and future releases, but the only one that seems appropriate to my problem was fixed in Beta 3... not sure if this is in the past or not.

Can anyone suggest a solution, or even just a clue? Is this a bug, recurring or fixed in beta?

Lois