Colleagues, Can you verify / clarify for me? >From reading changelogs it appears that tracking the shadowLastChange timestamp was not introduced until 1.2.11 - is that accurate? Is writing the timestamp something core server does automatically when the password is changed or is the client program supposed to change that attribute? I just inherited a running platform of 8 replicating servers across the country, which were set up with no password policies at all - for the moment I need to get 2500 users to change their passwords and begin tracking last change time. I'm enforcing password parameters / policy from a php app that can update the password for the user. Is there anything I can do with nsslapd-lastmod? Have any of you faced a similar problem? Many thanks for your advice. -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
