Red Hat Bugzilla – Bug 1290350
[User portal] No error message while leaving 'username:' and 'password:' fields blank
Last modified: 2016-02-18 06:07:39 EST
Created attachment 1104292 [details]
screen shot to refer the 'both the fields empty' scenario
Description of problem:
At userportal login page if user do not provide any credentials in 'username:' and 'password:' fields no error message is showing up, just an empty red square box pops up with error sign in it. It is applicable even when we leave one of those fields empty.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Go to userportal login page.
2. Leave both 'username:' and 'password:' fields or one of them empty.
3. Click on login.
No error message
error message should be present, some thing like "Please fill in all fields"
screenshot attached for reference.
Created attachment 1104293 [details]
screen shot to refer the 'one field empty' scenario
we have already fixed the issue for empty password (see bug 1254940 and bug 1251003), however this is probably fixed only for non-empty user-name.
need to make sure that the solution implemented for bug 1254940 and bug 1251003 applies for an 'empty-user-name and empty-password' situation as well.
(consult with Greg, assignee of bug 1254940 and bug 1251003, if necessary)
(In reply to Einav Cohen from comment #2)
> this is probably fixed only for non-empty user-name.
another possibility is that this issue was fixed somehow only for the web-admin login page and not the user-portal login page.
unrelated note: in 4.0, there are no user portal login page and web-admin login page - only SSO login page.
So for 4.0 - please ensure that an appropriate error message appears for the SSO login page.
for 3.6 - need a completely different patch that ensures that an appropriate error message appears for the web-admin and user-portal login pages.
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Created attachment 1116899 [details]
There still isn't any message, just red squares.
Tested on 3.6.2-10
So it appears the patch didn't get backported to the 3.6.2 branch, just 3.6. I will backport it to 3.6.2
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Verified on 3.6.3-1