Hi there,
I'm facing a problem with windows users whose password contains the spanish accented "n" (ñ). Neither the ldap directory or the password sync service complain at all , but the user is unable to auth in 389ds (latest version both 389-ds and windows pass sync). I've browsed the forums and disabled the 7bit-check plugin, but that does not seem to work either. Here's what I've found in the audit logs (please note the unhashed password entry):
Windows user password: funci0nA
time: 20120508080147
dn: uid=*******************
changetype: modify
replace: userPassword
userPassword: {SSHA}z8Ns6yOIY5N8JiZA7N53DWUCm6QCdBV083dXbA==
-
replace: modifiersName
modifiersName: cn=directory manager
-
replace: modifyTimestamp
modifyTimestamp: 20120508060323Z
-
replace: unhashed#user#password
unhashed#user#password: funci0nA
-
replace: entryusn
entryusn: 203032
However, with accented "n":
Windows user password: cañadelomo
time: 20120508080345
dn: uid=*****************
changetype: modify
replace: userPassword
userPassword: {SSHA}gD/DhJXnFiRsXl2KIooVPaSwG+1K9VjU8yxZ5Q==
-
replace: modifiersName
modifiersName: cn=directory manager
-
replace: modifyTimestamp
modifyTimestamp: 20120508060521Z
-
replace: unhashed#user#password
unhashed#user#password:: Y2HxYWRlbG9tbw==
-
replace: entryusn
entryusn: 203037
-
Why the difference when the spanish char is used, does it trigger something else in the sync process?
Regards!
Regards!
--
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
