Created attachment 850870 [details] screensot Description of problem: Log in button in the top right corner of "Red Hat Access: Support" page is NOT working. Version-Release number of selected component (if applicable): redhat-access-plugin-rhsc-2.1.2-3.el6rhs.noarch Red Hat Storage Console Version: 2.1.2-0.33.el6rhs How reproducible: 100% Steps to Reproduce: 1. Click on Cluster or Hosts tab and select any Cluster or Host 2. Click on "Red Hat Access: Support" 3. When the login pop-up appears, click on "Cancel" 4. Now click on "Please click to login to redhat.com" in the top right corner and click on "Log in". Actual results: The log in link is not taking us to the login page anymore. I could see the following in the logs: ----------------- WARN Thu Jan 16 11:42:10.395 IST 2014 [27.0.0.1:8702-8] [SynchronousDispatcher ] Unknown exception while executing GET /hosts java.lang.IllegalStateException: JBWEB000212: Session already invalidated at org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1267) at org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1233) at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:130) at org.ovirt.engine.api.common.security.auth.SessionUtils.setEngineSessionId(SessionUtils.java:74) at org.ovirt.engine.api.common.security.auth.Challenger.executeBasicAuthentication(Challenger.java:194) at org.ovirt.engine.api.common.security.auth.Challenger.preProcess(Challenger.java:116) at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:252) at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:499) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) at org.jboss.web.rewrite.RewriteValve.invoke(RewriteValve.java:466) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:488) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:420) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) at java.lang.Thread.run(Thread.java:744) ------------------- Expected results: The login page should pop-up once you click on "Please click to login to redhat.com" Additional info: Screenshot attached
There is a workaround for this -- If you close that window and bring it up again, you would be able to log in (unless otherwise, you are going to cancel again -- which is a purely ve test case and that fails )
Please review the edited doc text.
Approved
Verified as fixed in redhat-access-plugin-rhsc-3.0-0.el6rhs.noarch
Hi, Please review the edited text for technical accuracy and sign off.
Text Looks good
My previous comment was inaccurate, I was looking at the wrong field for the fixed-in version. The current text is appropriate.
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. http://rhn.redhat.com/errata/RHEA-2014-1277.html