Hi,
We have a radius server that reads the userPassword-attribute from ldap
to authenticate users. There is a strange phenomenon where sometimes the
answer from the ldap-server gives the wrong password hash algorithm. Our
global password policy storage scheme is set to SSHA. When I perform a
ldapsearch as directory manager I see that the password hash for a given
user is {SSHA}inserthashedpasswordhere. But when I run tcpdump to see
what our radius is being served I see {PBKDF2_SHA256}someotherhash
around 50% of the time. Sometime another request from radius a few
seconds after the first one gives the correct {SSHA} response.
This happened right after we updated from 389ds 1.2.2 to 1.4.4.
I am a bit stumped.
Thanks in advance,
Julian
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
