Bug 2174161

Summary: [RFE] Required to support both at a same time account inactivity and expiration.
Product: Red Hat Directory Server Reporter: Danish Shaikh <dshaikh>
Component: 389-ds-baseAssignee: mreynolds
Status: ON_QA --- QA Contact: LDAP QA Team <idm-ds-qe-bugs>
Severity: medium Docs Contact: Mugdha Soni <musoni>
Priority: medium    
Version: 11.0CC: bsmejkal, emartyny, idm-ds-dev-bugs, mreynolds, msauton, musoni, nsuryawa, pasik, pkulkarn, tbordaz, tmihinto
Target Milestone: DS12.3Keywords: Triaged
Target Release: dirsrv-12.3   
Hardware: x86_64   
OS: Linux   
Whiteboard: sync-to-jira
Fixed In Version: redhat-ds-12-9030020230711000312-1674d57 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Danish Shaikh 2023-02-28 18:38:02 UTC
Description of problem:

when creating Account Policy plug-in configuration entry stateAttrName can be either lastLoginTime or createTimestamp.

As a part of customer security compliancy, we are required to support both account inactivity and expiration. This is an urgent requirement which we are trying to realise through RHDS.



Version-Release number of selected component (if applicable):

RHDS 11.


How reproducible:

20.10.2. Account Inactivity and Account Expiration
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11/html/administration_guide/account-policy-plugin


Actual results:

- The alternate attribute  option is a fallback when the primary attribute does not exist.

- You can set a secondary attribute in altStateAttrName, that is checked if the primary one defined in stateAttrName does not exist"



Expected results:

As a part of customer security compliance, we are required to support both account inactivity and expiration. 


Additional info:

Comment 2 mreynolds 2023-03-29 14:52:46 UTC
*** Bug 2174160 has been marked as a duplicate of this bug. ***

Comment 6 mreynolds 2023-05-02 16:57:31 UTC
Upstream ticket:

https://github.com/389ds/389-ds-base/issues/5749