Hi,

I'm currently experiencing a problem with the module. We were able to successfully bind the module onto the AD server, however, after months of use, we are no longer able to bind this. We tested this, and we were able to do the binding, however, it looks as if the module no longer remembers the user details we used to do the binding. Any thoughts on how to address this? Thanks!

Comments

t-readyroc’s picture

We have an installation that's several years old now & just noticed the same exact behavior today. Using the same version of the plugin on RHEL6. Drupal 7.31/MySQL 5.1.73/PHP 5.3.3/Apache 2.2.15

ThomWilhelm’s picture

I believe we might be having the same problem, this seemingly stopped working for us without changing any configuration on the client side, what error message are you getting on the Drupal side?

LDAP bind failure for user . Error -1: Can't contact LDAP server

nhck’s picture

Same situation here.

RHEL6, PHP 5.3.3 with Suhosin v0.9.29, Apache 2.2

I tried to update to the dev package but that doesn't help.

ThomWilhelm’s picture

nhck can you confirm this just suddenly stopped working for you without any changes being made?

Basically we've had this module working nicely for well over a year now, and last weekend (around the 27th/28th) we started getting the error message I posted above. I'm doing some more debugging tomorrow to see if we can track down where the issue is.

I've been told on the LDAP server side they are getting a 'tls negotiation failure' message from our client IP address. However we don't have the startTLS option enabled in the Drupal config.

We are using version 7.x-1.0-beta12 of the module, however I've tested with 7.x-2.0-beta8 and it's the same error. Our environment: CentOS 6, PHP 5.3.16, Apache 2.2

t-readyroc’s picture

UPDATE: we figured out the issue on our end, & it had more to do with the provider than anything else. An NSS update apparently caused php-ldap to fail to load the libraries cleanly. It was actually just silently failing. An httpd restart solved the issue for us (the provider had patched w/o restarting the service).

PHP errors like the following were observed:

PHP Warning: ldap_start_tls(): Unable to start TLS: Can't contact LDAP server ...

nhck’s picture

I had the same problem t-readyroc expierienced. Now I have some other ones that I think are related to updating to the dev version :-/

ThomWilhelm’s picture

t-readyroc Thanks for that I can confirm restarting apache fixed this for us. Not Drupal module related at all.

Our server I believe was automatically patched with the following issue which caused this: http://bugs.centos.org/view.php?id=7647

ThomWilhelm’s picture

Status: Active » Closed (works as designed)

Closing as I believe this was a server issue nothing to do with the module.