Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/417https://bugzilla.redhat.com/show_bug.cgi?id=843576 (''Red Hat Directory Server'')
{{{
RFE Request
0. Proposed title of this feature request
Feature Request: forcing passwordmustchange attribute by non-cn=directory
manager
2. What is the nature and description of the request?
Feature Request: forcing passwordmustchange attribute by non-cn=directory
manager
3. Why does the customer need this? (List the business requirements here)
In an enterprise environment it is increasingly important that several
sub-departments are able to perform different tasks in an LDAP database. A
typical enterprise would like to give their Operations/Servicedesk department
the ability to reset user passwords when users call the Servicedesk when they
forgot theirs, but no more rights than that.
In terms of providing the aci's to a specific user for the Servicedesk this is
doable, but the 'User must change password after reset' flag in the password
policy of Directory Server only applies to resets done by the Directory
Manager. This user is akin to the 'root'/super user in Directory Manager and
this user has far too many rights for a department like Operations/Servicedesk
to handle. It poses a security risk.
An enterprise would need more flexibility with this attribute, for example set
it that several extra users trigger this flag when resetting another user's
password, or to make it in such a way that any user except the user itself
which changes the password, triggers the flag that the user must change
password at next login.
4. How would the customer like to achieve this? (List the functional
requirements here)
Functionality for forcing passwordmustchange attribute for all users.
5. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.
- Create a user, which has rights to change password for a sub-ou.
- Use above user to change password of x user, Try to login with x user.
6. Is there already an existing RFE upstream or in Red Hat bugzilla?
No
7. How quickly does this need resolved? (desired target release)
No time-line
8. Does this request meet the RHEL Bug and Feature Inclusion Criteria (please
review)
Yes
9. List the affected packages
389-ds-base
10. Would the customer be able to assist in testing this functionality if
implemented?
Yes
}}}
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-0416.html