... | ... | @@ -11,8 +11,6 @@ With ppolicy the password expires after some time and the only way to avoid this |
|
|
In both cases once expiration happened it’s too late and nothing is done.
|
|
|
The email is sent before expiration, with an alert delay which can be configured.
|
|
|
|
|
|
There may be some kind of conflict when people are using both shadowExpire, ppolicy and user-reminder.
|
|
|
|
|
|
### Fonctionality
|
|
|
|
|
|
1. In posix mode we look for **shadowExpire** and compare it with the actual date to find if its expired. If not expired we sent an alter to the user if not already send
|
... | ... | @@ -21,6 +19,10 @@ There may be some kind of conflict when people are using both shadowExpire, ppol |
|
|
|
|
|
If we need different pwdMaxAge values in the policies, we need to look at the **pwdPolicySubentry** attribute for the user(s) who are going to be expired.
|
|
|
|
|
|
### problems
|
|
|
|
|
|
There may be some kind of conflict when people are using both shadowExpire, ppolicy and user-reminder.
|
|
|
|
|
|
### Solution
|
|
|
|
|
|
* Add a bolean in the interface **use ppolicy** because **posix** is the default settings.
|
... | ... | |