-
-
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
Import location hierarchy from LDAP Active Directory user #17106
Comments
Please try with latest stable release. |
Thank you for your quick answer. |
Hi, |
Hi, |
Could you try if #17187 does solve your issue? It's maybe not the final fix, but at least we can be sure it's the same as the inventory related one. |
Could you check if #17187 solves your issue? |
Someone else has confirmed the fix works for users and inventory |
cedric-anne commented 35 minutes ago Could you check if #17187 solves your issue? Hi, I am still looking for how to proceed to apply this patch. Do I have to replace the files Inventory.php and CommonTreeDropdown.php ? Is there a way to find their path ? Thank you. |
I have just tried after replacing the two mentionned files. [2024-06-04 13:36:58] glpisqllog.ERROR: DBmysql::doQuery() in /var/www/glpi/src/DBmysql.php line 403 |
I take a quick look at the code. Is it possible that your LDAP is returning a non empty value that contains on spacing chars and/or |
Indeed, location field in our LDAP contains spacing chars and the character ">" as separator to specify the hierarchy |
What is the exact value ? We could add a test for it in our test suite. |
The exact value is : PS : I have switched the company name for privacy reason |
Hi, I have seen this morning that invetory does not work anymore since I applied the patch on June, 4th. When it did not work, here is the error message I found in php-errors.log : glpiphplog.CRITICAL: *** Uncaught Exception Error: Class "InventoryTestCase" not found in /var/www/glpi/front/inventory.php at line 48 |
Sounds like you made something wrong. |
The only relevant changes to apply are ones on It's a bad idea to put a patch test on production if you're not 100% sure what you are doing. |
I totally agree. |
There are tons of docs about aplying patches; this differs regarding of your environment. You can also just consider applying the few lines changes by hand. |
That's clear, thank you very much👍 |
Hello everyone, raise a ticket to GLPI In the LDAP server configuration for users, the default settings include the following AD attributes:" Global Criterion - LDAP Server is Server Name However, when adding a location attribute configuration: Surname: sn When checking the root rule, I noticed that the location criterion is missing from its criteria. LDAP Criteria: (AD)User ID I'm not sure if this is a bug. Let me know if you need any further assistance! His response was This issue has been closed as we only track bugs here. So if it is not a bug, where can I request this improvement for the next version of GLPI? |
|
I am not able to reproduce.
For me, the initial bug is fixed, but maybe there is something else to fix. Could you try to install the GLPI nightly build (https://nightly.glpi-project.org/glpi/10.0-aa4ad2c.tar.gz) on a test server and see if you can reproduce the issue ? |
We release 10.0.16 today; I consider initial issue is fixed; therefore I close this one. Feel free to open another issue with all details to reproduce issue on a fresh 10.0.16 install. |
Anyone has mentionned "sub entities" before; this is certainly another issue. Current issue is closed, please open a new one, with all details and how to reproduce problem on a fresh stable install. |
It seems to be the same issue as described in #9287. |
Code of Conduct
Is there an existing issue for this?
Version
10.0.4
Bug description
Hi,
Our current GLPI is version 10.0.14
We have only one instance : Production.
LDAP Active Directory synchronization is set up on our GLPI server.
This allow to import users and to automatically create location mapping the AD User field "City". The automatic creation of locations using hierarchy methode (using the symbol > to specify the child and parent) was working great on GLPI v9.
We migrated to GLPI v10 on December 2023.
Today, I discovered new locations in GLPI have automatically been created the day after we migrated to GLPI v10.
It seems that GLPI is no more able to "interpretate" correctly the symbol > to create hierarchy in locations, so GLPI created new locations.
I have read an article that seems to be similar to this case but I don't understand what I have to do to solve this issue : #15812
In addition, I understood this "bug" was solved in v10.0.11 but as we are running a more recent version, I am confused.
Could you please tell me if the separator symbol > is still the one to user ?
If yes, how could I solve the issue ?
Thank you very much for your help.
Relevant log output
No response
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: