[JBoss JIRA] (GTNPORTAL-2998) Error in server.log when trying to "SignOut" but session expired
by Marek Posolda (JIRA)
Marek Posolda created GTNPORTAL-2998:
----------------------------------------
Summary: Error in server.log when trying to "SignOut" but session expired
Key: GTNPORTAL-2998
URL: https://issues.jboss.org/browse/GTNPORTAL-2998
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.6.0.Beta01
Reporter: Marek Posolda
Assignee: Marek Posolda
Fix For: 3.6.0.Beta02
1) Go to http://localhost:8080/portal and login as root
2) Let session expire (or delete JSESSIONID cookie from browser cookies)
3) Click to "SignOut"
This will end with exception
{code}
12:43:30,117 ERROR [portal:PortalRequestHandler] (http--127.0.0.1-8080-1) Error while ending request on all ApplicationLifecycle: java.lang.IllegalStateException: User is not authenticated
at org.gatein.wci.ServletContainer.logout(ServletContainer.java:211) [wci-wci-2.3.1.CR05.jar:2.3.1.CR05]
at org.exoplatform.portal.application.PortalLogoutLifecycle.onEndRequest(PortalLogoutLifecycle.java:55) [exo.portal.webui.portal-3.6.0.Beta02-SNAPSHOT.jar:3.6.0.Beta02-SNAPSHOT]
at org.exoplatform.portal.application.PortalLogoutLifecycle.onEndRequest(PortalLogoutLifecycle.java:37) [exo.portal.webui.portal-3.6.0.Beta02-SNAPSHOT.jar:3.6.0.Beta02-SNAPSHOT]
at org.exoplatform.portal.application.PortalRequestHandler.processRequest(PortalRequestHandler.java:216) [exo.portal.webui.portal-3.6.0.Beta02-SNAPSHOT.jar:3.6.0.Beta02-SNAPSHOT]
at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:159) [exo.portal.webui.portal-3.6.0.Beta02-SNAPSHOT.jar:3.6.0.Beta02-SNAPSHOT]
at org.exoplatform.web.WebAppController.service(WebAppController.java:329) [exo.portal.component.web.controller-3.6.0.Beta02-SNAPSHOT.jar:3.6.0.Beta02-SNAPSHOT]
at org.exoplatform.portal.application.PortalController.onService(PortalController.java:108) [exo.portal.webui.portal-3.6.0.Beta02-SNAPSHOT.jar:3.6.0.Beta02-SNAPSHOT]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNSSO-25) Exception during SAML global logout if session expired
by Marek Posolda (JIRA)
Marek Posolda created GTNSSO-25:
-----------------------------------
Summary: Exception during SAML global logout if session expired
Key: GTNSSO-25
URL: https://issues.jboss.org/browse/GTNSSO-25
Project: GateIn SSO
Issue Type: Bug
Affects Versions: 1.3.2.Final
Reporter: Marek Posolda
Assignee: Marek Posolda
Fix For: 1.3.3.Final
Steps to reproduce:
1) Setup from https://docs.jboss.org/author/display/GTNPORTAL36/SAML2 with "Portal as SAML2 SP and SAML2 IDP"
2) Let session expire on www.sp.com (For example delete JSESSIONID cookie in browser)
3) Click SignOut . We will end with exception in server.log like:
{code}
12:21:22,080 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http-www.sp.com-192.168.2.7-8080-1) An exception or error occurred in the container during the request processing: java
.lang.RuntimeException: PLFED000146: Error during processing the SAML Handler Chain.
at org.picketlink.identity.federation.PicketLinkLoggerImpl.samlHandlerChainProcessingError(PicketLinkLoggerImpl.java:1113)
at org.picketlink.identity.federation.web.process.ServiceProviderBaseProcessor.process(ServiceProviderBaseProcessor.java:182)
at org.picketlink.identity.federation.bindings.tomcat.sp.AbstractSPFormAuthenticator.generalUserRequest(AbstractSPFormAuthenticator.java:567)
at org.picketlink.identity.federation.bindings.tomcat.sp.AbstractSPFormAuthenticator.authenticate(AbstractSPFormAuthenticator.java:293)
at org.picketlink.identity.federation.bindings.tomcat.sp.AbstractSPFormAuthenticator.authenticate(AbstractSPFormAuthenticator.java:253)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:455) [jbossweb-7.0.13.Final.jar:]
at org.gatein.sso.integration.SSODelegateValve.invoke(SSODelegateValve.java:155) [sso-integration-1.3.3.CR03-SNAPSHOT.jar:1.3.3.CR03-SNAPSHOT]
at org.gatein.portal.security.jboss.PortalClusteredSSOSupportValve.invoke(PortalClusteredSSOSupportValve.java:88) [exo.portal.component.web.security-jboss-3.6.0.Beta02-SNAPSHOT.
jar:3.6.0.Beta02-SNAPSHOT]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]
Caused by: org.picketlink.identity.federation.core.exceptions.ProcessingException: PLFED000022: Principal Not Found
at org.picketlink.identity.federation.PicketLinkLoggerImpl.samlHandlerPrincipalNotFoundError(PicketLinkLoggerImpl.java:1036)
at org.picketlink.identity.federation.web.handlers.saml2.SAML2LogOutHandler$SPLogOutHandler.generateSAMLRequest(SAML2LogOutHandler.java:359)
at org.picketlink.identity.federation.web.handlers.saml2.SAML2LogOutHandler.generateSAMLRequest(SAML2LogOutHandler.java:89)
at org.picketlink.identity.federation.web.process.ServiceProviderBaseProcessor.process(ServiceProviderBaseProcessor.java:176)
... 15 more
{code}
This is picketlink bug, but we can handle it in gatein-sso as well
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (GTNPORTAL-2997) Skip redirection in LoginServlet if user is already authenticated and response is commited
by Marek Posolda (JIRA)
Marek Posolda created GTNPORTAL-2997:
----------------------------------------
Summary: Skip redirection in LoginServlet if user is already authenticated and response is commited
Key: GTNPORTAL-2997
URL: https://issues.jboss.org/browse/GTNPORTAL-2997
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: SSO
Affects Versions: 3.6.0.Beta01
Reporter: Marek Posolda
Assignee: Marek Posolda
Fix For: 3.6.0.Beta02
In case of some SSO providers (like SAML) it could happen that user is already authenticated and HTTP response is already commited. In this case we should skip redirection of HttpResponse in LoginServlet because response has been already redirected by SAML Valve
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months