2012/12/18 Ramesh Kumar <[email protected]>: > Hello Team, > > I just implemented ltb-ldap. Everything is working fine and as expected > except the password policy check which was the whole cause to shift to LTB. > > When I am running ./checkLdapPwdExpiration.sh script its show me below output: > > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: No password change > date for silva > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: No password change > date for sonta > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: No password change > date for toby > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: No password change > date for temp > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: No password change > date for ulack > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: No password change > date for vapurman > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: No password change > date for vveck > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: --- Statistics --- > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: Users checked: 65 > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: Account expired: 0 > Dec 18 04:59:26 util05 ./checkLdapPwdExpiration.sh[14878]: Account in > warning: 0 > > Does that mean, I don't have proper password policy in place, if so can you > please point me in right direction so that I can verify my settings with? >
Hi, it means some of your users do not have yet changed their password (not since you set up password policy), so no password change date is written in their entry. You can ignore these errors. Clément. _______________________________________________ ltb-users mailing list [email protected] http://lists.ltb-project.org/listinfo/ltb-users
