Hey everyone,

I've been trying to figure out the solution to this little annoyance, and I do appologize if anyone else has come acrossed it and have already provided a solution, however I have been unable to locate one.

I have managed to get the module installed and working, however whenever someone logs in they do recieve the following login error:

warning key_exists()[function key-exists]. The second argument should be either an array or an object in ../sites/all//modules/ldap_integration/ldapauth.module on line 957.

The following is the code on that line:

$mail = $ldap_user[$ldapauth_ldap->getOption('mail_attr')][0];

I've noticed that the email address does not get populated. However when I add the hack to fix that, it crashes all of Drupal. I also have noticed that when I add in an email address that I do not get the above message... Any and all help is greatly appreciated.

Thanks for your help,

Pete

Comments

PMatwyuk’s picture

PMatwyuk commented
Title: WARNING Key_Exists().. » Base DN over written when user logs in
Category: bug » support
Priority: Normal » Critical

Hey everyone,

I've come accross yet another issue. My drupal install currently has 12 users for beta testing and initial setup. Out of those 12, 4 are having a login issue, and recieve the issue stated above. I have went in to accounts that dont receive the error, and compaired them to the 4 that are receiving it. The difference is those that are receiving it dont have a LDAP User DN set, or an email set.

This being the case I assumed that simply editing the fields would allow me to fix the solution. I had them login and sure enough they received the same error. I had them go to there account page, and I saw that the LDAP User DN and the email were once again both blank. I again filled it in, had them log in, and samething happend. The next step I thought was to see what the user database had to say. I went to the MySQL database looked at the user's table and saw no connection code for ldap in their user rows. I then went into there profiles on Drupal, updated it again, and then went to check the database. Sure enough the connection string was in the database. I then had them log in, again to recieve the error, I went back to the database for a final time and saw that the connection string had been removed.

Everytime they submit there login details the connection string is removed, however are still authenticated properly, but receive the error listed above.

Any assistance will be greatly appreciated.

Pete

johnbarclay’s picture

johnbarclay commented
Status: Active » Closed (won't fix)

Closing 5.x issues to clean out issue queue.