-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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. |
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: