Bug 2174160 - [RFE] Required to support both at a same time account inactivity and expiration.
Summary: [RFE] Required to support both at a same time account inactivity and expiration.
Keywords:
Status: CLOSED DUPLICATE of bug 2174161
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Directory Server
Version: 11.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-28 18:38 UTC by Danish Shaikh
Modified: 2023-03-29 14:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-29 14:52:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Danish Shaikh 2023-02-28 18:38:01 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 1 mreynolds 2023-03-29 14:52:46 UTC
closing as duplicate of 2174161

*** This bug has been marked as a duplicate of bug 2174161 ***


Note You need to log in before you can comment on or make changes to this bug.