Problem in activating a new generated ldap account
Zach Nelson reported there was an issue to activate his account:
hash string Kv9aZuLOdu$tO3 doesn't match our record.
but the account was activated:river:conf tao$ ldapsearch -x -h ldap.ecoinformatics.org -b o=unaffiliated,dc=ecoinformatics,dc=org uid=zach-nelson
- extended LDIF #
- base <o=unaffiliated,dc=ecoinformatics,dc=org> with scope subtree
- filter: uid=zach-nelson
- requesting: ALL #
- zach-nelson, unaffiliated, ecoinformatics.org
cn: Zachary nelson
gecos: Zachary nelson,,,
- search result
result: 0 Success
- numResponses: 2
- numEntries: 1
We need figure out why the hash string didn't match and why the account was activated even though the hash string didn't match.
#3 Updated by Jing Tao over 6 years ago
- Status changed from New to Closed
"^x" is part of the hash string.
It seem user successfully activated his account:
I was able to activate by copying the url into my web browser. I am linked
to knb now and creating some data packages in morpho.
In the email we ask users to copy the url if he/she can't activate the account by click the link.
Maybe first time the user didn't copy the url fully?
I will close the bug.