I have had LDAP integration working for about six months now. Awesom module.

About a week ago I noticed that LDAP was no longer updating user info, so I upgraded from alpha 2 to the latest dev. It then occurred to me that I had installed Content Profile at about the time things started going haywire.

When a user logs in, LDAP grabs the email and username (which are defined in the server settings) but nothing else. I get the error: "User view: user [username]'s data could not be read in the LDAP directory" when anyone logs in

I have checked the attributes and the group mapping and everything looks OK. Any thoughts? Thanks.

Comments

gettysburger’s picture

gettysburger commented

Oh, and I got this error:
implode(): Invalid arguments passed in /srv/www/htdocs/sites/all/modules/ldap_integration/ldapgroups.admin.inc on line 123.

...on this page:
/admin/settings/ldap/ldapgroups/edit/1

Not sure if this is related.

miglius’s picture

miglius commented

Did you run upgrade.php script?

gettysburger’s picture

gettysburger commented

Yes, thanks for asking. I ran it again, just for fun and the behavior is the same.

It does validate the user against my network and sees the username and email, which are set in the global settings.
It does NOT map the LDAP Group the Drupal Roles.
It does NOT grab the other attributes.

gettysburger’s picture

gettysburger commented
Status: Active » Fixed

I got it to work.

In Configure LDAP Server/Login Procedue/Base DNs: I changed:

ou=MYADMIN
o=HGJ

..to be all on the same line, separated by a comma

ou=MYADMIN,o=HGJ

...and it WORKED.

parkej60’s picture

parkej60 commented

I am having pretty much this exact same issue, except I'm not getting any errors. The data just doesn't map. I'm able to authenticate but like I said it will not map any data. Since you said your issues started when you installed Content Profile I removed it. I also have uninstalled this module and reinstalled, re-configured the authentication numerous times and no matter what it will not map the data. Any suggestions?

miglius’s picture

miglius commented

LDAP data module is integrated with the core profile module, not with a contrib content_profile module.

gettysburger’s picture

gettysburger commented

I no longer think that Content Profile has anything to do with it. The fix for us was putting the server configuration in a line separated by commas, instead of on separate lines, as the instructions suggest.

In Configure LDAP Server/Login Procedue/Base DNs:

Don't do this:

ou=MYADMIN
o=HGJ

..do this

ou=MYADMIN,o=HGJ

Have you tried that?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.