Red Hat Bugzilla – Bug 1032533
[RHSC] An additional username-password prompt is seen after entering the username and password in the login page
Last modified: 2015-05-13 12:54:25 EDT
Description of problem:
After entering the login username and password in the login page of RHSC, a second prompt is seen asking for username and password. This is seen sometimes.
The second prompt looks like the prompt seen when trying to use the REST API.
Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.24.master.el6_5
Steps to Reproduce:
1. Navigate to the login page of the administrator portal.
2. Enter the login details for admin@internal.
3. Click on login.
A second prompt is seen asking for username and password, similar to the prompt seen when trying to use the REST API.
After clicking on login, the user should be logged in.
Created attachment 826566 [details]
Created attachment 827155 [details]
Observed this issue with CB9 also. Attaching logs.
Created attachment 828602 [details]
engine logs ( CB9 )
This bug may become an issue for automation, if this screen comes up. So, it may be needed to be fixed from that point of view.
But if time constraint comes, we will take a call then...
This is same as the RHEVM 1011058.
This is reproducible only in firefox 17. I am not seeing this issue in latest versions of Firfox starting from Firefox 21.
The corresponding framework change that is required in framework space, is going to happen in 3.4 (not in 3.3), we will defer this bug to after Corbett. It will be taken out of Corbett and appropriate doc-text would be added.
Other point to note is : this issue should not have any impact on Automation, because in that there is no chance for session timeout
Please review the edited Doc Text and sign off.
Do text looks good.
Fixed in upstream ovirt-engine 3.4 release.
Tested by setting UserSessionTimeOutInterval=1. Got logged out automatically after 1 minute, logged in again. Did not see the second prompt.
I have edited the doc text. Kindly verify it for technical accuracy and sign-off.
Doc text looks good.
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.