We are seeing this error in our log file. Can someone please explain what it means and what we need to do to prevent it from occuring?
Thank you,
Peter
Hi Peter,
Can you check whether you have any Techs with usernames which are the same as their linked Client record usernames? Since release 12.5.2 they should be different as all login validation should go via the Client record only.
This from the 12.5.2 Release Notes
Before you install this upgrade, ensure that all techs have client accounts (authenticated through LDAP) linked to their tech accounts. Also, ensure that all tech usernames do not match any new or existing client usernames. After the upgrade, all techs must access their tech account using their client account or their WHD tech username and WHD password (which can be reset using the secure password reset logic).
Thank you for the prompt response. Currently Techs have the same user name as their Client credentials. We will change those and see if that resolves the issue.
Do let me know if this resolves this question.
I am very pleased to say that by giving our Techs unique Usernames (name_whd) we have eliminated the Tech.setLdapConnection() error from our error logs. Users and Techs did not experience any change in performance or behavior, though it has only been 1 week with this change in place.
