Metacat

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

1. extended LDIF #
2. LDAPv3
3. base <o=unaffiliated,dc=ecoinformatics,dc=org> with scope subtree
4. filter: uid=zach-nelson
5. requesting: ALL #

1. zach-nelson, unaffiliated, ecoinformatics.org
   dn: uid=zach-nelson,o=unaffiliated,dc=ecoinformatics,dc=org
   cn: Zachary nelson
   sn: nelson
   givenName: Zachary
   mail: z.j.nelson2010@gmail.com
   employeeNumber: Kv9aZuLOdu$tO3^X
   uidNumber: 30056
   gidNumber: 30056
   loginShell: /sbin/nologin
   homeDirectory: /dev/null
   objectClass: top
   objectClass: person
   objectClass: organizationalPerson
   objectClass: inetOrgPerson
   objectClass: posixAccount
   objectClass: shadowAccount
   o: unaffiliated
   gecos: Zachary nelson,,,
   uid: zach-nelson

1. search result
   search: 2
   result: 0 Success

1. numResponses: 2
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.