dsdb: Use PSO maxPwdAge for operational msDS-PasswordExpiryTimeComputed
authorTim Beale <timbeale@catalyst.net.nz>
Thu, 19 Apr 2018 01:51:36 +0000 (13:51 +1200)
committerGarming Sam <garming@samba.org>
Wed, 23 May 2018 04:55:32 +0000 (06:55 +0200)
commit1ebfe6957fd8995e7c7690c842e196e6c649b6db
treeeebeaf13318befc6be6b283f6a9c12066565fe18
parent3b849f87f7237a3677338075309abb1355a4d9ef
dsdb: Use PSO maxPwdAge for operational msDS-PasswordExpiryTimeComputed

When calculating the Password-Expiry-Time, we should use the PSO's
max-password-age setting, if one applies to the user.

This is code may be inefficient, as it may repeat the PSO-lookup work
several times (once for each constructed attribute that tries to use
it). For now, I've gone for the simplest code change, and efficiency can
be addressed in a subsequent patch (once we have a good test to measure
it).

Signed-off-by: Tim Beale <timbeale@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Garming Sam <garming@catalyst.net.nz>
selftest/knownfail.d/password_settings [deleted file]
source4/dsdb/samdb/ldb_modules/operational.c