Red Hat Bugzilla – Bug 1138688
[windows] unable to log in to JON from FF
Last modified: 2015-11-01 19:44:18 EST
Created attachment 934773 [details] win_login Description of problem: [windows] unable to log in to JON from FF (versions 23 and 32 checked) Version-Release number of selected component (if applicable): JON 3.3 ER02 How reproducible: always Steps to Reproduce: 1. log in to JON GUI from firefox on w2008 2. log in to JON GUI from chrome on w2008 3. Actual results: after step1. cannot log in -- no error on gui, no log on server & agent logs after step2. log in to gui -- URL is changed from IP:7080/coregui/login to IP:7080/coregui/login#Dashboard Expected results: log in to gui -- URL is changed from IP:7080/coregui/login to IP:7080/coregui#Dashboard Additional info: screen-shots attached
Created attachment 934774 [details] win_login_crome
The screenshot is not conclusive. In attachment 934774 [details], I see that you are logged in both browsers. Can you provide more details and additional screenshots? Is it possible that you were already logged in prior to the step 1? Can you please try on a clean w2008 system?
Worked with Armine to reproduce but without success; tried this on 2 separate Windows machines. It could have been a caching issue on the intial box. However, we uncovered that the login screen does not look good on low screen resolution. Armine, can you please close this BZ and open a new focused only on the login page layout at low resolutions?
The issue with the login page layout at low resolutions was captured already in bug 1135018. Please close this bug if there are no futher issues to investigate.
There must have been a missunderstanding. In firefox, in Win 2008 server i am still unable to log in to JON. Cleaning cache does not fix this issue. The issue is still valid. moving back to assigned.
Armine, can you please post a new screenshot? The current one does not give any indication of what the problem is.
video with reproduction attached
Moving into ER05 as didn't make the ER04 cut.
Cannot reproduce the FF issue on: VirtualBox: Windows 8.1 and FF23 FF32 FF33 (none of them) Windows XP FF33 BrowserStack: Windows 7 FF23 FF32 FF33 However, I reproduced the Chrome issue on w8.1, Chrome40dev using BrowserStack and even on my box, so I'll address this.
branch: master link: https://github.com/rhq-project/rhq/commit/9e915a46d time: 2014-10-16 17:48:50 +0200 commit: 9e915a46d700b5a26777cdc82d83eb8f44b28760 author: Jirka Kremser - jkremser@redhat.com message: [BZ 1138688] - [windows] unable to log in to JON from FF - adding some magic to make the logging in working on newer browsers. Basically, some waiting (20ms) needed to be added before the redirect. Because of the fact that /login and /Coregui.html both uses the same gwt module some logic was added to distinguish between them and prevent the UI from rendering when user is still on the /login page.
branch: release/jon3.3.x link: https://github.com/rhq-project/rhq/commit/1cb21219e time: 2014-10-16 18:48:28 +0200 commit: 1cb21219e54eb156668d02f9829d61fe4b1531b4 author: Jirka Kremser - jkremser@redhat.com message: [BZ 1138688] - [windows] unable to log in to JON from FF - adding some magic to make the logging in working on newer browsers. Basically, some waiting (20ms) needed to be added before the redirect. Because of the fact that /login and /Coregui.html both uses the same gwt module some logic was added to distinguish between them and prevent the UI from rendering when user is still on the /login page. (cherry picked from commit 9e915a46d700b5a26777cdc82d83eb8f44b28760) Signed-off-by: Jirka Kremser <jkremser@redhat.com>
release/jon3.3.x commit 412c0a1a87c4641271e14dabf6ddeb9c948df602 Author: Jay Shaughnessy <jshaughn@redhat.com> Date: Thu Oct 16 14:20:13 2014 -0400 [1138688] Fix cherry-pick issue that lost necessary import
Moving to ON_QA as available to test with the latest brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=394734
Created attachment 949306 [details] windows_login_er05
Could not reproduce either, but the issue happens only if browser machine has incorrect time set (I am able to reproduce if time is set +- 8hours further). Not sure if I am able to fix this (the fact, that we require the client to have correct time+time zone set).
Libor fixed the time sync on my windows env -- thank you Libor.
Created attachment 950402 [details] win_ff_login