Description: The Directory server handles automatic account inactivity through the Account Policy plugin. Through this plugin, one has the flexibility to determine whether an entry should be inactivated depending on the value of a particular attribute (referenced by the value of stateattrname). Moreover, this plugin also provides the functionality to store the last login time of an entry (also stored in the attribute referenced by the value of stateattrname). This request is for an improvement in functionality, in which this dual role of the stateattrename attribute is split into two separate attributes. This would provide functionality that is inachievable with the current semantics.
Example:
If account lockout is based on passwordExpirationTime under Account Policy plugin then lastLoginTime does not get updated. The configuration used for passwordExpirationTime is given below.
dn: cn=config,cn=Account Policy Plugin,cn=plugins,cn=config objectClass: top objectClass: extensibleObject cn: config alwaysrecordlogin: yes stateattrname: abc altstateattrname: passwordExpirationTime specattrname: acctPolicySubentry limitattrname: accountInactivityLimit accountInactivityLimit: 2592000
In above configration stateattrname has set with dummy value hence when the dummy is not available then altstateattrname is checked for alternate value. The above configuration help is implemention account lockout base on passwordExpirationTime and the passwordExpirationTime does not get update with customer login time. But this configuration does not allow lastLoginTime to be updated.
git patch file (master) 0001-Ticket-47714-RFE-Update-lastLoginTime-also-in-Accoun.patch
git patch file (master) 0002-Ticket-47714-CI-test-add-test-case-for-ticket-47713.patch
Reviewed by Mark (Thank you!!)
Pushed to master: ae3a53f..39b6a18 master -> master commit 533f250275c745fd2b0decc74b6d560502209495 commit 39b6a18b4c4cf53fd3ac52b5e331e2e043cd9d1f
Cleaned up unused method in the test script ticket47714_test.py: 39b6a18..65216ab master -> master commit 65216aba18cc66c5b36d11ab2202b620d4df6b4c
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.3 - 8/14 (August)