Created attachment 809846 [details] server, engine & jasper logs Description of problem: Dashboard TAB in webadmin is empty, after logging to user portal, dashboard works fine. Additional Input: there is a security popup requires rhevm-admin crednetial in two cases: -During login to reports admin -Creating reports from webadmain (Single Virtual Machine Resources (Over Time) for example) ovedo: "Dashboard is indeed empty. When opening a report, it shows that the user is logged in, but it gives a popup to ask for username password of basic authentication. ... iirc, the solution was to remove some filter from the filter chain. It is also weird that in the bean configuration the engine URL is: http://localhost/OvirtEngineWeb/ValidateSession But a truststore is configured. Is that configured like that intentionally?" Version-Release number of selected component (if applicable): 17.1: rhevm-dwh-3.3.0-13.el6ev.noarch rhevm-reports-3.3.0-10.el6ev.noarch jasperreports-server-pro-5.5.0-2.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 809897 [details] ovirt-engine.conf
I've investigated the issue. From the provided information it looks like the setup configured everything correctly. @Oved: Can you please send me the log of your reports setup? Thanks.
(In reply to Alex Lourie from comment #2) > I've investigated the issue. From the provided information it looks like the > setup configured everything correctly. > > @Oved: > > Can you please send me the log of your reports setup? > > Thanks. It is not my setup. It is Barak's setup. What seemed weird to me is that the URL of the engine wasn't secured (i.e. http and not https). Is that intentionally? Barak - please attach the logs.
Rechecked the problematic setup. The setup utility configured system correctly. On my machine, the dashboard works fine in both Firefox and Chrome. On Barak's machine Firefox showed an empty dashboard, while Chrome showed it ok. Private Firefox session showed it ok. Unintentionally Firefox was restarted, and then showed the page correctly. Recommending to close as not an issue, and reopen if repeats.
agrees
(In reply to Oved Ourfali from comment #3) > What seemed weird to me is that the URL of the engine wasn't secured (i.e. > http and not https). Is that intentionally? not sure if related: we have this bug: bug 1018111 (which is occurring due to a jboss EAP 6.2.0 bug 1018365). @Oved/Alex/Yaniv: - do you think that these bugs are related to the "URL of the engine wasn't secured" that you have discovered? - do you think that the JBoss bug may be related to the behavior originally described in this bug?
(In reply to Einav Cohen from comment #6) > (In reply to Oved Ourfali from comment #3) > > What seemed weird to me is that the URL of the engine wasn't secured (i.e. > > http and not https). Is that intentionally? > > not sure if related: we have this bug: bug 1018111 (which is occurring due > to a jboss EAP 6.2.0 bug 1018365). > > @Oved/Alex/Yaniv: > - do you think that these bugs are related to the "URL of the engine wasn't > secured" that you have discovered? The URL I'm talking about was the one defined in the reports server. Doesn't seem related to issues about other components. But will let other to reply on that in case I'm mistaken. > - do you think that the JBoss bug may be related to the behavior originally > described in this bug?