Greetings,
I seem to be running across this debug issue. I'm confused why the bind_method would be "%bind_method", instead of an integer, where it an integer in other places. The "Error:Success" is also a little confusing.
user@example.gov : Trying server example_ldap where bind_method = %bind_method. Error: Success
Here is the entire report log. It appears that the module connects twice to the LDAP server? I understand that it connect to the Drupal db, but it finds nothing, so it moves onto the AD as it should. What is frustrating is that under the user tab (Test LDAP User Configuration) and I able to query and retrieve user data.
user: Login attempt failed from xx.xxx.xx.162.
Anonymous (not verified) ldap_authentication: %username : Failed ldap authentication…
Anonymous (not verified) ldap_authentication: user@example.gov : Authentication result is 3 (Sorry,…
Anonymous (not verified) ldap_authentication: user@example.gov : Trying server bor_ldap where bind…
Anonymous (not verified) ldap_server: ldap_search() call: base_dn: DC=bor,DC=doi,DC=net,…
Anonymous (not verified) ldap_authentication: user@example.gov : Success at connecting to bor_ldap
Anonymous (not verified) ldap_authentication: user@example.gov : Trying server bor_ldap where bind…
Anonymous (not verified) ldap_authentication: user@example.gov : Existing Drupal User Account not…
Anonymous (not verified) ldap_authentication: user@example.gov : Beginning authentication....
Anonymous (not verified) ldap_sso: Cookie present
Anonymous (not verified) ldap_sso: Path is valid
Anonymous (not verified) ldap_sso: SSO Boot assumed
Anonymous (not verified) ldap_sso: CLI or logged in user
Thanks in advance, this project is being worked on a team of developers and system admin for a enterprise organization, hopefully we can contribute or document our findings.
Drupal: 8.2.7
LDAP Module: 3.0.0-alpha3
Comments
Comment #3
grahlHi
I really recommend you try the DEV version since that contains many fixes and a beta1 will be released shortly.
I agree that the error message is misleading since it will report success even if we do not find a user. For example, when I just entered random information, I saw the message. The search request seems to be valid in that scenario though since that empty search does not return an actual LDAP error and thus you see success.
Please note that the integers you see should be gone in many cases due to improvements in the yaml configuration (you need to run updb for those). LDAP errors should now be mostly consistently reported by name and code in parenthesis.
Please reopen if you still encounter an actual error during authentication.
Comment #4
gunner_chad commentedokay, we will adjust and report back out findings.
Comment #5
gunner_chad commentedWe had success by using the DEV version. In addition to, bring in an Active Directory Admin. Thanks.