problem with passwords.py solved

[Matthias Dieter Wallnöfer]

Hi Nadya,

you can propose such a patch - but keep in mind: also the SAMR password 
tests would need a change in order to pass on an unconfigured Windows 
Server. I think: either all password tests integrate such a mechanism - 
or we remind the user to set it manually. Since I don't like to have a 
halfway solution.

Sorry - I've really forgotten to tell it (it's some time back when I 
changed this) - we do always have "minPwdAge" set to "0" in order to 
perform the password tests. This is also one important difference which 
we could have noticed if we would have looked into Zahari's AD outputs :).

Matthias

Nadezhda Ivanova wrote:
> Hi Matthias,
> With Kamen's help, we determined that the reason the tests was not 
> passing in my environment is that it appears by default minPwdAge is 
> set to one day. therefore we simply cannot change the user password 
> several times in one second, and get constraint violation. So it turns 
> out, we have to set/reset minPwdAge as well at the beginning and end 
> of the testsuite to avoid the kind of problems I had. I'll do this in 
> acl.py to handle the negative tests, and if you don't mind will add 
> the same to passwords.py. We should not forget, however, that this 
> means that Samba 4 does not take minPwdAge into account the same way 
> Windows does, which is maybe a bug...
>
> Regards,
> Nadya