Hello Quanah, Thank you very much, I will try that and let you know on Monday, I really appreciate it. Have a great weekend all.
Thanks, Ed -----Original Message----- From: Quanah Gibson-Mount <[email protected]> Sent: Friday, September 18, 2020 4:46 PM To: CLARKE, ED C <[email protected]>; [email protected] Subject: RE: Issues with resetting user password --On Friday, September 18, 2020 2:42 PM -0700 Quanah Gibson-Mount <[email protected]> wrote: > Nothing you've provided shows any attempt to connect to the ldap > server using an SIMPLE BIND with the user DN > "uid=foxdiv,ou=People,dc=att,dc=com" and a password. As an example, the correct way to test the user password change went through would be something like: ldapwhoami -x -H ldap://ldap.example.com:389/ -D uid=foxdiv,ou=People,dc=att,dc=com -W If slapd is running on ldaps, adjust the URI accordingly. If it's on port 389 but requires startTLS, add the -ZZ option, etc. You will be prompted for the password for the LDAP user. If the operation succeeds, then the password was correctly updated in LDAP. It sounds as though you may be attempting *nix <-> ldap integration, but that hasn't been specified. Regardless, the above ldapwhoami command is the next step in confirming whether or not the password was correctly changed and accepted on the user side. If that works, and you're attempting the *nix<->ldap integration and *that* is not working, it would imply that the integration is not configured correctly. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.symas.com&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=BQ_G-uwK8fNzomGg07UAOw&m=Y28PgXtiljLwY4wK27SGBoxO1QfiORYohCxZ9o64WsM&s=CqcrKk1NdaFebMowKt5QjliLvA_RCVEadq8MIoK_s4U&e= >
