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.
DescriptionJeeva Kandasamy
2013-11-07 10:26:19 UTC
Created attachment 820984[details]
html source
Description of problem:
On IPA WebUi login page "username" and "password" marked as mandatory fields on the HTML source code. However it is not working for the "username" field. If you keep the "username" filed empty it is not validating in client side. It is taking it to server side for authentication.
Version-Release number of selected component (if applicable):
ipa-server-3.3.2-3.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. navigate on your browser(I used firefox) https://<hostname>/ipa/ui/index.html
2. keep empty "username" field
3. enter some value on "password" field
4. Click on "Login" button.
Actual results:
If you keep the "username" filed empty it is not validating in client side. It is taking it to server side for authentication.
Expected results:
These type validation should happen on client side.
Additional info:
Screen shot and html source code files are attached.
Thanks for your report. The ability to enter this form without login++password is intentional - it translates to log in with Kerberos as written in the dialog. When user and password is entered, it logs in with user+password.
However, you are right that you should not be able to fill in just password, the dialog should require user to be filled as well. I will open an upstream ticket for that.
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-0442.html
Created attachment 820984 [details] html source Description of problem: On IPA WebUi login page "username" and "password" marked as mandatory fields on the HTML source code. However it is not working for the "username" field. If you keep the "username" filed empty it is not validating in client side. It is taking it to server side for authentication. Version-Release number of selected component (if applicable): ipa-server-3.3.2-3.el7.x86_64 How reproducible: always Steps to Reproduce: 1. navigate on your browser(I used firefox) https://<hostname>/ipa/ui/index.html 2. keep empty "username" field 3. enter some value on "password" field 4. Click on "Login" button. Actual results: If you keep the "username" filed empty it is not validating in client side. It is taking it to server side for authentication. Expected results: These type validation should happen on client side. Additional info: Screen shot and html source code files are attached.