Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Description of problem:
Low priority!
It seems that the "Save User" button gets disabled during one - and only one circumstance - when the entered passwords don't match. Otherwise there are plenty of other methods by which the user can enter incomplete data and the Save User button is enabled. Wondering but if there should be some uniformity.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. +New User; observe state of "Save User" button.
2. Enter Username; observe state of "Save User" button - hit save user
3. Enter "redhat" in password field; observe state of "Save User" button.
4. Enter "fibble" in confirm field; observe state of "Save User" button.
5. Enter "redhat" in confirm field; ; observe state of "Save User" button - hit save user
6. Enter "username" in Email address field; observe state of "Save User" button - hit save.
Actual results:
During most of these steps, user creation will be rejected, which is ostensibly correct. However, when password fields don't match, the "Save user" button is disabled.
Expected results:
It seems to me that we should either
(a) disable Save User button anytime we have incomplete data, or
(b) modify the apparently one-off behavior that disables the "Save User" button when passwords are incorrect. Of course, this would require error-checking to be enabled on password submit (don't create a user when Password != Confirm)
Additional info:
In all, very low priority, but somewhat odd user experience