Re: pwdChangedTime not defined when creating new entry
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday 9 March 2020 10:19, Clément OUDOT <clement.oudot(a)worteks.com> wrote:
Le 06/03/2020 à 17:47, Quanah Gibson-Mount a écrit :
> --On Friday, March 6, 2020 8:47 AM +0000 Manuela Mandache
> manuela.mandache(a)protonmail.com wrote:
>
> > Hello Clément,
> > Thanks for your answer. Well, if you don't get the same behavior as I
> > do,
> > it does seem I have a configuration issue. But what configuration issue
> > can that be? Where should I look for it?
[...]
> I might start with seeing if there are noticable differences
between
> the 2.3 and 2.4 ppolicy man pages. And perhaps Clément can share the
> config he was working with. :)
[...]
dn: cn=default,ou=ppolicies,dc=example,dc=com
[...]
pwdMaxAge: 31536000
[...]
Hi Clément and hi all,
Thanks for your suggestions.
After all this time, I finally found my configuration problem: My directory
was in a test environment and I didn't want to be bothered with password
expiration, so I set pwdMaxAge at about 100 years (36,500 days). In seconds,
this exceeds 2^31-1, and most of the ppolicy features were out of service.
Regards,
Manuela