Contrib.social

LDAP authentication is successful, but the LDAP-authenticated user cannot log in. Meanwhile, it can log in if flood attempts block the account.

Open on Drupal.org →
Created on 25 November 2023, 12 months ago
Updated 19 June 2024, 5 months ago

Problem/Motivation

I use this LDAP module (8.x-4.5) on Drupal 10.1.6. Before updating, it used to work well; however, all LDAP users have been unable to log in recently even though LDAP authentication itself is successful with no issue. What confuses me is that LDAP authenticated users can log in once the flood-attempts-block mechanism in the core blocks the accounts.

Here is the log file for failure and success cases:
1) Failure case:
ldap_authentication zsxxxx : Beginning authentication
ldap_authentication zsxxxx: Drupal user account found. Continuing on to…
ldap_authentication zsxxxx: Trying server xxx_xxx_ldap with user…
ldap_authentication zsxxxx: Authentication result is "Authentication… (Message: Authentication result is "Authentication successful (no issue)")
user Login attempt failed for zsxxxx.

2) Success case:
ldap_authentication zsxxxx : Beginning authentication
ldap_authentication zsxxxx: Drupal user account found. Continuing on to…
ldap_authentication zsxxxx: Trying server xxx_xxx_ldap with user…
ldap_authentication zsxxxx: Authentication result is "Authentication…
user Flood control blocked login attempt for uid 5 from 148… (Here the account is blocked by Flood control)
user Session opened for zsxxxx.

I also tested mixed mode (Drupal and LDAP) and LDAP-only authentication; it didn't solve the problem. I would appreciate it if there is a way to figure out the problem. This might be the case only for our system, though.

💬 Support request
Status

Closed: works as designed

Version

4.5

Component

Code

Created by

🇯🇵Japan htakamur

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @htakamur
  • Comment 12 months ago →
    🇺🇸United States bluegeek9

    Hi @htakamur,

    Did you upgrade Drupal or the LDAP module? What was the last version that worked?

  • Comment 12 months ago →
    🇯🇵Japan htakamur

    Thank you. I just used "composer update" without enough caution, so I was unsure which update caused the problem. I checked various combinations of core and the LDAP module and found those are not problems.

    It turns out that another login-related module, i.e., "Mail Login," which enables email address login, was the reason. By removing the mail_login module, the login problem mentioned above disappears. If mail_login is installed again, the login problem emerges again. FYI, another email login module, "Email Registration," seems OK with the simultaneous use of LDAP.

    I should have checked this before submitting this issue. Sorry for bothering you.

  • Status changed to Closed: works as designed 12 months ago
  • Comment 12 months ago →
    🇺🇸United States bluegeek9
  • Comment 6 months ago →
    🇳🇿New Zealand dexiecarla

    The problem stated in this ticket is happening to me, anyone can help?

    Also, there were times admin/config/people/ldap/server page,
    In server reachable column, status is "Binding issues, please see log."
    sometimes its "Server available"

    I am really unsure about this irregularity.

    I even played around refreshing the page couple of times, sometimes its connected, sometimes its not.

  • Comment 5 months ago →
    🇫🇷France NicociN

    Also facing the issue.

  • Comment 5 months ago →
    🇫🇷France NicociN

    Oh, htakamur you were right about mail_login ! (didn't carefully read...)
    Thanks !

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024