-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
10.0.6 - Sync existing users error LDAP import when change the ldap user password in configuration #14075
Comments
I am not an expert in PHP coding, I try we never know, it really blocks us in the implementation of our GLPI instance which worked well in 10.0.0.5 THKS @cconard96 Do you know if is it related to the changes made to bug #12794 or #11497 ? |
We add to the AuthLDAP.php
We no longer have the error but another error `[2023-02-14 13:13:06] glpiphplog.WARNING: Test logger [2023-02-14 13:13:08] glpiphplog.WARNING: *** PHP User Warning (512): LDAP search failed with error (1) Operations error in E:\glpi\src\AuthLDAP.php at line 1871 [2023-02-14 13:13:08] glpiphplog.WARNING: *** PHP Warning (2): ldap_search(): Search: Operations error in E:\glpi\src\AuthLDAP.php at line 1867 [2023-02-14 13:13:08] glpiphplog.WARNING: *** PHP User Warning (512): LDAP search failed with error (1) Operations error in E:\glpi\src\AuthLDAP.php at line 1871 |
see #14049 |
@Nol-go Thks but ko ?... |
To test only installation of a new 10.0.6 instance and a new blank database : the problem persists. In case we have regenerated a new GLPI Key (bin/console glpi:security:change_key) but : the problem persists. We restored the virtual machine (Still in 10.0.6) the sync works BUT as soon as the LDAP login account is changed or its password it no longer works |
@cedric-anne @cconard96 Hello gentlemen, I'm sorry to bother you, but after checking all the configurations the LDAP synchronization no longer works, do you think of a bug that a future fix could fix? |
@Tols78 if you want a very quick response, please consider taking a subscription. Otherwise, wait for a response, community support is on a best effort basis. |
The problem has just been fixed, at the beginning he used the samaccountname attribute for the rootDN and his distinguishedName had spaces. We think the Cache made it magicaly work until today, since it stopped working, the moment it was cleared. Sorry for the disturbance. |
We fixed some issues recently related to encoding issues on LDAP operations. Could you try to install GLPI nightly build on a test server and see if problem persist? |
Ive installed GLPI 10.07-dev (10.0‑bcd40ee.tar.gz | 2023‑04‑01) nightly and still experiencing the LDAP sync/search issue. |
Hi, Could you try to reproduce the issue on GLPI 10.0.7? If problem persist, could you review your LDAP configuration to ensure it has not been altered by any migration? |
Cedric-anne I have tried the following: LDAP connection filter: (&(objectClass=user)(objectCategory=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) Test scenario on 10.0.8 right after update: Test2: The error only seems to appear after changing the password+clear and then saving LDAP settings. The password is 100% correct, I've tested using a 3rd partly LDAP query tool with the LDAP filter above and its succeeds If there are any other test cases you would like to perform please let me know |
If you check the |
Hi @cedric-anne The proceed to LDAP seems to test fine, but the search is an issue when trying to import new users. |
Hi, Can you try #14563? |
I've tried and still getting the same error. Also tried the latest nightly 10.0-ea41dca still no luck :-( |
#14561 mays help to prevent errors when LDAP objects are not found (due to applied filters for instance), and may help to identify other errors. It is a huge patch, but could you try it, and give the exact log that is produced during import? |
Hi Cedric-Anne, |
You can find a build containing this fix here: https://github.com/cedric-anne/glpi/actions/runs/4827869219 This build correspond to the current nightly build + the #14561 patch. |
No feedback from a while, closing. |
Code of Conduct
Is there an existing issue for this?
Version
10.0.6
Bug description
Hello,
Since i change user DN for connect to LDAP
Synchronization of existing users via search filter: KO
Synchronization In console mode via glpi:ldap:synchronize_users KO
Test connection ldap : OK
In graphical mode the LDAP filter is transformed
(& (samaccountname=*) (&(objectClass=user)(objectCategory=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2))))
Becomes
(&
(samaccountname=*) (&(objectClass=user)(objectCategory=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2))))``Relevant log output
Page URL
Just go to the In graphical mode LDAP filter
Steps To reproduce
Just go to the In graphical mode LDAP filter
Your GLPI setup information
GLPI 10.0.6 ( => C:\glpi)
Installation mode: TARBALL
Current language:fr_FR
Operating system: Windows NT
PHP 8.1.10
Setup: max_execution_time="300" memory_limit="512M" post_max_size="8M" safe_mode="" session.save_handler="files"
upload_max_filesize="200M"
Software: Microsoft-IIS
Server Software: mariadb.org binary distribution
Anything else?
Anything else?
No response
The text was updated successfully, but these errors were encountered: