LDAP bind failure for user userdn=, pass=. [#2780393]

Hi,

I updated to 7.x-2.0-beta11 from 7.x-2.0-beta8+14-dev, and now it is throwing a notice for the non-ldap user:

LDAP bind failure for user userdn=, pass=.

Which was not an issue in the past.

I have used "Bind with Users Credentials" in the server setting.
Any fix?

Comment	File	Size	Author
#8	ldap-bind_failure-2780393-8.patch	716 bytes	PascalAnimateur
#8	7.x-2.x: PHP 5.3 & MySQL 5.5, D7 19 pass, 13 fail PHP 5.4 & MySQL 5.5, D7 21 pass PHP 5.5 & MySQL 5.5, D7 21 pass PHP 5.6 & MySQL 5.5, D7 21 pass
#6	ldap-bind_failure-2780393-6-D7.patch	806 bytes	mmarler
#6	7.x-2.x: PHP 5.3 & MySQL 5.5, D7 19 pass, 14 fail PHP 5.4 & MySQL 5.5, D7 Skipped, branch did not pass for 4 weeks PHP 5.5 & MySQL 5.5, D7 Skipped, branch did not pass for 4 weeks PHP 5.6 & MySQL 5.5, D7 Skipped, branch did not pass for 4 weeks
#5	ldap_servers.install.patch	806 bytes	mmarler
#5

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

8 August 2016 at 00:55

LeafLin created an issue. See original summary.

Comment #2

LeafLin CreditAttribution: LeafLin commented 8 August 2016 at 01:10

Sorry,

Just want to clarify it was not a problem in 7.x-2.0-beta8, but has been throwing the message since 7.x-2.0-beta8+14-dev.

Comment #3

jwillard CreditAttribution: jwillard commented 8 August 2016 at 14:58

Yes, I can also confirm this issue. I also have the same setting of "bind with users credentials" checked. I tried beta9 and beta11 and they both appeared to be throwing this error message in the system log. I did not have this issue as of beta8.

Comment #4

mmarler CreditAttribution: mmarler commented 12 August 2016 at 14:30

I can confirm this too. Also, after updating from beta8 the status report is saying, "Connection: Failed, check logs for details."

Comment #5

mmarler CreditAttribution: mmarler commented 12 August 2016 at 16:40

File	Size
ldap_servers.install.patch	806 bytes

Here's a patch. The issue only seems to be with the status report trying to bind user credentials. Since the report is generated after the user has logged in there is no user dn or password to bind with since ldap doesn't store passwords. A work around is to do an anonymous bind.

Comment #6

mmarler CreditAttribution: mmarler commented 12 August 2016 at 17:28

File	Size
ldap-bind_failure-2780393-6-D7.patch	806 bytes
7.x-2.x: PHP 5.3 & MySQL 5.5, D7 19 pass, 14 fail PHP 5.4 & MySQL 5.5, D7 Skipped, branch did not pass for 4 weeks PHP 5.5 & MySQL 5.5, D7 Skipped, branch did not pass for 4 weeks PHP 5.6 & MySQL 5.5, D7 Skipped, branch did not pass for 4 weeks

1 file was hidden/shown/deleted

File	Size
ldap_servers.install.patch	806 bytes

Renaming patch

Comment #7

GaëlG

he/him

French

Lille, France

CreditAttribution: GaëlG at Insite commented 30 August 2016 at 13:25

Status:

Active

» Reviewed & tested by the community

The last patch works. Thank you!

Comment #8

PascalAnimateur CreditAttribution: PascalAnimateur commented 23 November 2016 at 02:07

File	Size
ldap-bind_failure-2780393-8.patch	716 bytes
7.x-2.x: PHP 5.3 & MySQL 5.5, D7 19 pass, 13 fail PHP 5.4 & MySQL 5.5, D7 21 pass PHP 5.5 & MySQL 5.5, D7 21 pass PHP 5.6 & MySQL 5.5, D7 21 pass

Re-roll patch from #6 so it applies cleanly in drush make file

Comment #9

grahl

he/him

Zürich

CreditAttribution: grahl at Namics commented 15 February 2017 at 17:41

Right, well, isn't the anonymous bind conditional on the specific server configuration? I think it doesn't make sense to set to anonymous for service account bind, is it?

Comment #10

grahl

he/him

Zürich

CreditAttribution: grahl at Namics commented 15 February 2017 at 17:43

Status:	Reviewed & tested by the community	» Closed (duplicate)
Related issues:		+#2838389: ldap_servers_requirements will always fail to bind when using Bind with Users Credentials option

I'm marking this as a duplicate of https://www.drupal.org/node/2838389, let's fix it over there.