Ppolicy functions that not work

Hello, We have some functions in ppolicy that not work.

• Expiry warning delay
• Safe modify (old password is not ask when we change the password)

changed milestone to %49

added PJ1802-0188 label

changed the description

changed due date to June 06, 2019

hello @MCMic,

have we solution for those missing fonctionalities today ?

Cheers

added 5m of time spent at 2019-06-04

If pwdExpireWarning is readable, we may be able to detect this and show a warning dialog at login in this case.

pwdSafeModify is harder because it means changing the password edition form based on this setting. It also means having a different form depending on who is editing since we still want admin and managers to be able to edit passwords. And we’ll get a weird case when the manager/admin edit himself. It may also mean disabling password recovery in this case.

added 5m of time spent at 2019-06-06

removed due date

changed due date to June 12, 2019

hello @MCMic,

so it's not trivial. i say lets see if pwdExpireWarning is readeable and we can use it for displaying a warning in this case.

the pwdSafeModify i propose we don't touch it right now.

Cheers

added 5m of time spent at 2019-06-06

https://gitlab.fusiondirectory.org/fusiondirectory/fd/blob/1.4-dev/include/functions.inc#L502 and https://gitlab.fusiondirectory.org/fusiondirectory/fd/blob/1.4-dev/html/main.php#L113 are two ways of doing the same thing, we should clean POSIX expiration handling code and integrate ppolicy support in it.

So this method: https://gitlab.fusiondirectory.org/fusiondirectory/fd/blob/1.4-dev/include/class_userinfo.inc#L869 should take ppolicy into account. (See https://gitlab.fusiondirectory.org/fusiondirectory/fd/blob/1.4-dev/plugins/personal/generic/class_user.inc#L400 to see how to get active ppolicy for a given user DN)

@bmortier Should ppolicy expiration be tested even if handleExpiredAccounts is off? (This is «Use account expiration» boolean in «Password settings» section in configuration main tab)

added 1h 30m of time spent at 2019-06-18

«Expiry warning delay» is waiting for test in fd#6001, and «Safe modify» is a separate issue, that should be looked at in fd#5841, so closing this.

closed

removed due date