Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1254723
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
1. Proposed title of this feature request [RFE] sssd: better feedback form constraint password change 3. What is the nature and description of the request? When changing a password: $ passwd Changing password for user testuser. Current Password: New password: Retype new password: Password change failed. Server message: Please make sure the password meets the complexity constraints. passwd: Authentication token is no longer valid; new one required As sssd know this was a problem with the password already being used. (Thu Aug 13 14:56:06 2015) [sssd[be[LDAP]]] [sdap_exop_modify_passwd_done] (0x0080): ldap_extended_operation result: Constraint violation(19), Password is in history of old passwords It would be better to give feedback on this $ passwd Changing password for user user. Current Password: New password: Retype new password: Password change failed. Server message: Password is in history of old passwords And I would also remove the following passwd: Authentication token is no longer valid; new one required 4. Why does the customer need this? (List the business requirements here) User able to figure out that there password they are trying to change to is in the password history list.
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: no => 0 owner: somebody => mzidek patch: 0 => 1 review: True => 0 selected: => status: new => assigned testsupdated: => 0
milestone: NEEDS_TRIAGE => SSSD 1.13.2
Patch was submitted, should be included in 1.13.1
milestone: SSSD 1.13.2 => SSSD 1.13.1
resolution: => fixed status: assigned => closed
Metadata Update from @jhrozek: - Issue assigned to mzidek - Issue set to the milestone: SSSD 1.13.1
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3803
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.
Login to comment on this ticket.