Red Hat Bugzilla – Bug 911677
Lock page has no indication that a failed password was entered
Last modified: 2014-01-21 14:26:30 EST
+++ This bug was initially created as a clone of Bug #911669 +++ Description of problem: The lock page currently just stays as is when a bad password was entered with no indication that the password is bad Version-Release number of selected component (if applicable): 2.6.0 How reproducible: Always Steps to Reproduce: 1. login as admin 2. lock screen from status page 3. enter incorrect password and choose unlock Actual results: screen does nothing Expected results: screen should refresh with a "Incorrect Password" message and remove the password Additional info:
http://gerrit.ovirt.org/13942
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Test version: rhevh-6.5-20131031.1.0 ovirt-node-3.0.1-7.el6.noarch Test steps: 1. Lock screen 2. Enter an incorrect password 3. Dialog appears with "The provided password was incorrect." 4. Close the dialog 5. The password field is empty 6. Provide the correct password 7. Select unlock 8. the screen is unlocked. So the bug is fixed, change bug status to VERIFIED.
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. http://rhn.redhat.com/errata/RHBA-2014-0033.html