LDAP Servers (and CAS): Anonymous binding has stopped working [#1772444]

All of our LDAP sites have started failing to bind anonymously after updating to beta 12. Making them bind as a user works, so that is my temporary workaround, but it used to work fine anonymously (and that would be our preferred choice). I haven't had chance yet to test it on dev to see if its that same, and I am not really sure what would cause it to fail, but the error that the module is displaying is that it failed to bind. I have confirmed that you definitely can still bind anonymously to the servers, so its something the module is doing differently.

--Ash

Comments

Comment #1

13rac1 commented 31 October 2012 at 22:25

Status:

Active

» Postponed (maintainer needs more info)

If this is still a problem, please provide all required details on the issue.

Comment #2

johnbarclay commented 26 February 2013 at 19:01

Status:

Postponed (maintainer needs more info)

» Closed (cannot reproduce)

Comment #3

vinmassaro commented 17 December 2013 at 18:10

Version:	7.x-1.0-beta12	» 7.x-2.0-beta6
Issue summary:	View changes
Status:	Closed (cannot reproduce)	» Active

This is an issue for us as well. I just started noticing entries in watchdog when users were being created. We were previously on LDAP 7.x-2.0-beta3, and when updating to 7.x-2.0-beta6, anonymous bind has stopped working. We have users being created when logging in via CAS. The bind appears to be working, since their first and last names are being pulled in using the CAS Attributes module. LDAP is only logging this, which doesn't give me much to debug:

LDAP bind failure for user userdn=, pass=.

On 7.x-2.0-beta3, testing the LDAP server returns a full page of data correctly. I then update LDAP via drush. I test the server again and it returns nothing, not even an error. It just returns me back to re-submit the page again. Thanks.