Bug 1309362

Summary: User should be notified for wrong password in password reset page
Product: Red Hat Enterprise Linux 7 Reporter: Jan Kurik <jkurik>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.3CC: akasurde, ekeck, ipa-maint, jcholast, ksiddiqu, pvoborni, rcritten
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.2.0-15.el7_2.8 Doc Type: Bug Fix
Doc Text:
After the user entered an incorrect old password when resetting the password in the IdM web UI, the password was not changed but IdM did not inform the user about the failure. Now, IdM displays an error message.
Story Points: ---
Clone Of: 1293870 Environment:
Last Closed: 2016-05-12 09:58:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1293870    
Bug Blocks:    
Attachments:
Description Flags
Using wrong current password
none
Using wrong new password none

Description Jan Kurik 2016-02-17 15:43:37 UTC
This bug has been copied from bug #1293870 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 6 Abhijeet Kasurde 2016-03-17 12:12:09 UTC
Verified using IPA server ::

ipa-server-4.2.0-15.el7_2.10.x86_64


Steps used to verify ::

1. Create a new IPA user using IPA admin
2. Login as a new IPA user
3. UI will redirect to password change page
4. use different new password, this will notify user with warning message.

Comment 7 Abhijeet Kasurde 2016-03-17 12:13:24 UTC
Created attachment 1137365 [details]
Using wrong current password

Comment 8 Abhijeet Kasurde 2016-03-17 12:13:50 UTC
Created attachment 1137367 [details]
Using wrong new password

Comment 10 errata-xmlrpc 2016-05-12 09:58:23 UTC
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/RHBA-2016-1036.html