View Issue Details

IDProjectCategoryView StatusLast Update
0012556mantisbtauthenticationpublic2011-08-05 02:41
Reporterpredated Assigned Toatrol  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
OSWindowsOS VersionServer 2008 
Product Version1.2.3 
Summary0012556: SYSTEM WARNING: ldap_search(): Search: Operations error
Description

Unable to authenticate to Active Directory LDAP using config below:

/ LDAP Login Settings /
$g_login_method = LDAP;
$g_ldap_server = 'xx.xx.xx';
$g_ldap_port = '389';
$g_ldap_root_dn = "OU=XX,DC=XX,DC=XX,DC=XX";
$g_ldap_uid_field = 'sAMAccountName';
$g_ldap_bind_dn = 'CN=system_account';
$g_ldap_bind_pw = 'password';
$g_ldap_protocol_version = 3;
$g_ldap_follow_referrals = OFF;
$g_use_ldap_email = ON;
$g_use_ldap_realname = ON;

Steps To Reproduce

Attempt to log in to Mantis with any ID.

Additional Information

I just upgraded to 1.2.3 this morning. I was 1.2.2 previously, and I was getting the same results.

I did modify core/ldap_api.php manually to set LDAP_OPT_PROTOCOL_VERSION to 3, and LDAP_OPT_REFERRALS to 0. These changes had no effect on the error.

I have other applications authentication to LDAP on this same server, using the same settings (wordpress, dokuwiki, drupal).

Log file entry:
2010-11-23 13:14 EST ldap Binding to LDAP server
2010-11-23 13:14 EST ldap Attempting connection to LDAP server 'xx.xx.xx' port '389'.
2010-11-23 13:14 EST ldap Connection accepted to LDAP server
2010-11-23 13:14 EST ldap Setting LDAP protocol to to ldap server to 3
2010-11-23 13:14 EST ldap Attempting anonymous bind to ldap server
2010-11-23 13:14 EST ldap bind to ldap server successful
2010-11-23 13:14 EST ldap Searching for (&(sAMAccountName=xxxxxx))
2010-11-23 13:14 EST ldap ldap_search() returned false.

TagsNo tags attached.

Activities

dregad

dregad

2010-11-23 16:16

developer   ~0027464

I am running LDAP on AD without any problems for months. Are you sure you are using the exact same parameters for your other apps ?

you wrote: $g_ldap_bind_pw but the actual parameter is $g_ldap_bind_passwd, is that a typo ?

I never had the case where ldap_search failed, but if problem persists, maybe adding a call to ldap_error in ldap_api after the failed search may help.

predated

predated

2010-11-24 10:39

reporter   ~0027476

Silly me. Guess I needed to go over my config file 1001 times, instead of 1000.

It was just that little typo that cost me hours of frustration and an erroneous bug report.

Thanks dregad.

dregad

dregad

2010-11-24 10:42

developer   ~0027477

Heh. ;-)
You're welcome.

dregad

dregad

2011-04-27 04:37

developer   ~0028700

atrol, maybe you should mark this as resolved...

atrol

atrol

2011-04-27 06:24

developer   ~0028705

thanks Damien