- General
-
Ideas
+2
Completed
Pouvoir changer le chemin DN d'un compte AD
Bonjour,
Un compte importé dans GLPI a un chemin DN (DN de l'utilisateur), ce chemin sert pour la connexion.
Problème, si la structure de l'active directory change, le chemin DN n'est plus bon dans GLPI.
ex : si CN=alain le grand,OU=Billetterie,OU=toto,OU=Utilisateurs,DC=domaine,DC=lan devient CN=alain le grand,OU=commercial,OU=toto,OU=Utilisateurs,DC=domaine,DC=lan.
Ou alors si il y a pas exemple une migration de l'AD vers un autre domaine.
Il serait bon que dans GLPI le chemin DN soit un champ modifiable que l'administrateur peut modifier si besoin pour correction.
Sinon il faut supprimer l'utilisateur et le réimporter mais je pense que les liens vers ses anciens tickets sont perdus.
Customer support service by UserEcho
please post in English
Hello,
An imported Account in GLPI had a DN path (DN of the User) , this path is use for the connection and we can see the path in GLPI
Problem, if the structure of active directory had change , the DN path is not more good in GLPI.
eg if CN = Alain large , OU = Ticket , OU = toto , OU = Users , DC = domain , DC = lan
BECOMES
Alain CN = great OR = shopping , OU = toto , OU = Users , DC = domain , DC = lan .
Or a AD migration domain. What It Would be good in GLPI if the adminostrator can manually change the DN to do a correction. Otherwise Should DELETE The User and add it again but i think the link beetween the user and tickets is lost.
Hello,
The main problem here is not the DN but the unique ID !
Users can be moved in different OU (like when changing of location or departement). GLPI must import SID and use it to distinct user, and synchroniser new DN automatically !
Hello,
We're introducing a new "sync field" for users. This field can be, for example, the userID.
So if you migrate from one directory to another, as long as the sync fields value remains the same the DN and login field will be updated.
https://github.com/TECLIB/glpi/tree/ldap_new_identifier