A question about Importing Requester Password via CSV when using LDAP Authentication
We are in the process of evaluating Service Desk Plus (SDP)
Some of our LDAP fields do not seem to import automatically. For our organization we use 'Entity' in our LDAP directory where SDP would use Site, and we use 'Location' where SDP uses 'Department'.
I've found that in the manual importation process I can map our Entity field to the Site field and I can map our 'Location' field to the 'Department' field. As long as FirstName, LastName, UserName, are the same then the 'Requester's' information is updated.
The question I have regards the 'Password' field. I'm required to have that field for the importation process. When I ran my test, I simply mapped the SDP 'Password' field to the LastName field. How does the importation of the Password field affect the users ability to log in when we have login via LDAP Authentication set?
I've not yet got the actual Requester login via LDAP Authentication to work so I'm not sure if this breaks the login process or not.
Some of our LDAP fields do not seem to import automatically. For our organization we use 'Entity' in our LDAP directory where SDP would use Site, and we use 'Location' where SDP uses 'Department'.
I've found that in the manual importation process I can map our Entity field to the Site field and I can map our 'Location' field to the 'Department' field. As long as FirstName, LastName, UserName, are the same then the 'Requester's' information is updated.
The question I have regards the 'Password' field. I'm required to have that field for the importation process. When I ran my test, I simply mapped the SDP 'Password' field to the LastName field. How does the importation of the Password field affect the users ability to log in when we have login via LDAP Authentication set?
I've not yet got the actual Requester login via LDAP Authentication to work so I'm not sure if this breaks the login process or not.