How can LDAP credentials become invalid after clone

Dirk Hillmer
Tera Contributor

We cloned from PROD to TEST and noticed that the LDAP authentication was not possible anymore. We use the same credentials for all instances. The investigation showed that the credentials were cloned with the wrong password values.
Any ideas?

4 REPLIES 4

priyasunku
Kilo Sage

@Dirk Hillmer  check if the password has been overwritten or emptied because of clone. just give the credentials once again and try.

 

 

If my answer solved your issue, please mark my answer as Correct & 👍Helpful

 

 

The LDAP config was cloned from PROD to TEST. After the clone the passwort value is not the same on TEST and PROD. The password value has been incorrectly cloned. 

It is not emptied.. it is overwritten by a wrong value.
But the wrong value is not comming from PROD. It seems to be generated during the Clone.

But there is no exclusion, preserver or clean-up script that changes anything.

IvanC2
Tera Contributor

Ran into the same issue myself. Tested everything possible because I was certain the clone could not cause the password to be incorrect. Hopefully others see this and find the resolution quicker.

We also noticed same issue cloned from Sandiago to Utah and LDAP started not working with invalid credentials. When we try to use same account to login directly to server it works but not from ServiceNow LDAP configuration when we test connection it throws invalid credentials and locking the user account.