Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1775285
Description of problem: Most of the LDAP vendors have implemented the pwdReset attribute. Some customers are relying on this attribute to detect if a password must be changed by the user. Version-Release number of selected component (if applicable): RHDS 10. How reproducible: Always Steps to Reproduce: Requesting the attribute pwdReset returns no result. Actual results: pwdReset is not present in RHDS 10. # grep -i pwdReset /usr/share/dirsrv/schema/* # Expected results: Implement the attribute "pwdReset" from RFC draft-behera-ldap-password-policy Additional info: https://tools.ietf.org/html/draft-behera-ldap-password-policy-10
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1775285
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.3 (was: 0.0 NEEDS_TRIAGE)
https://pagure.io/389-ds-base/pull-request/50916
Commit 7923698 relates to this ticket
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Commit 3ddcc62 relates to this ticket
Fix schema definition to not allow USER MODIFICATION
ab22bc8..a87fc40 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3965
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.