Closed (outdated)
Project:
Lightweight Directory Access Protocol
Version:
7.x-2.4
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Apr 2019 at 14:19 UTC
Updated:
13 Dec 2020 at 13:09 UTC
Jump to comment: Most recent
Comments
Comment #2
casperone commentedComment #3
grahlHuh weird that the release version is not selectable there.
Can you please give a full log from ldap_help? See the issue creation guidelines.
Comment #4
casperone commentedI have enabled ldap_help and cannot seem to find the where to generate the full log. Could you point me in the right direction? I have reviewed the creation guidelines as well and am missing where it says how to generate the full log
Thank you in advance
Comment #5
grahl/admin/config/people/ldap/help
Just to be safe, you did run the update hook, right? Did it tell you you needed to resave your credentials and if so, did you do so? The invalid connection points in that direction.
Comment #6
casperone commentedI have found /admin/config/people/ldap/help, there are a number of sub-tabs including watchdog and issue reporting. I have enabled "Enabled Detailed LDAP Watchdog logging.", yet when looking at LDAP Watchdog Errors and Notifications I do not find any messages. I am clearly missing a big step?
You mention the "update hook", I am not familiar with this. I also ran into this problem after updating using "drush -y up". Where can I confirm the "update hook" was run?
Comment #7
grahlIf you added detailed LDAP watchdog logging you should see dozens of new messages in Recent log messages per login attempt.
You run the update hooks with updb, see ldap_servers_update_7209() for what it did. It told you to update your credentials, if necessary. Which seems like the culprit if your first error is that it cannot establish a connection.
Comment #8
danielvezaJust for future consideration for the maintainers - When I ran this update with drush it didn't tell me anything. So I had a broken ldap connection with no clues as to why it was broken.
Comment #9
grahlClosing issue as outdated due to no further development on 7.x, if you feel this issue is still relevant and you are willing to work on a patch and/or debug the problem, please reopen.