Since i've enabled logging in with ldapauth, i try logging in with an account on the AD server and it just freezes at:

http://example.com/?q=node&destination=node

Comments

t1s’s picture

*Note: the page is completely blank.

scafmac’s picture

I'm not sure I follow you - are you logged in or not? If it is redirecting you to q=node, then I would assume you are. Of course it doesn't really make sense that it would have both q=node & destination=node, but I almost always turn on clean urls, so I'm not all that familiar with the typical parameters when clean urls are disabled.

Typically when nothing is displayed, it is a programming error or incorrect AD settings and there should be some useful information in the webserver error log. Start there - also check the drupal log to see if the authentication succeeded or not. I presume you can still log in as the super user (uid=1).

Post any error messages as well as your sanitized AD settings.

t1s’s picture

Since i've checked logs and it doesn't show anything in drupal, I'm assuming that I don't have the settings correct. I've gotten other things to be able to work with AD, but this is proving a bit more challenging.

For our jabber server it requires a base DN, an administrator DN, and adminstrator password, (Cant recall if it needs the administrator dn or just an account with privileges) server ip, and port number. Since this is all it needs for that, that's all that I know. I know the obvious ones, but are the other ones i know applicable?

scafmac’s picture

If the settings are wrong, I would expect to see an LDAP error in the Drupal logs. You checked in the Drupal logs as well as the webserver logs and found nothing? Are you absolutely sure?

I'll need some more details - you may have entered the correct AD info, but with strange characters. For example there used to be a bug that if there was a carriage return at the end of the base dn, it would bomb, but that was patched a while ago. Please tell me all of the settings you entered except for the password which I assume you confirmed is correct.

Do you have the devel module installed? If not replace the dsm line below with:

drupal_set_message(print_r($ldapauth_ldap, true));

The devel modules is just a bit nicer that's all. Though if you use it, you will have to give permissions to anonymous users as well as authenticated users for debugging this since you are unable to login, it will only display the debugging info if anonymous users' have perms for it.

So edit the ldapauth.module file. Go to approximately line 589 & add the extra line below - note to only use dsm if you have the devel module installed.

    // Get distinguished name
    $dn = _ldapauth_login2dn($login_name);
    dsm($ldapauth_ldap);     // ******* this is the extra line
    if (empty($dn)) {
      continue;
    }

Save the file & try to login. It might not show the content when the blank screen appears, but when you go to the home page after trying to login, it should still show the queued drupal message. Post the output.

ajudson’s picture

i was getting this same error... for me it was just i'd forgotten to install & enable the ldap module with php.ini

cgallo’s picture

I had this same problem, i suggest you execute phpinfo() and make sure ldap is configured there.

bytemybits’s picture

I'm having the same problem. I have an older version of ldap auth working on another server with the same settings. My logs show that a session is being opened but I too am left on a blank page at /node?destination=node. When I edit the url directly to go back to the home page I'm not logged in. If I try a user/pass combination I know is incorrect I get the "Sorry. Unrecognized username or password." as expected. There's nothing in the web server error logs. I get the same result if I go to /user and enter my credentials there, the only difference is I'm then left on /user with a blank page.

bytemybits’s picture

I resolved this by upgrading the PHP version I was using. I can't remember where I found that was the problem. I would consider the issue closed.

johnbarclay’s picture

Status: Active » Closed (won't fix)

Closing 5.x issues to clean out issue queue.