[JBoss JIRA] Created: (GTNPORTAL-1027) GateIn+SSO integration: Blank screen when SSO ticket is not valid (OpenSSO)
by Marek Posolda (JIRA)
GateIn+SSO integration: Blank screen when SSO ticket is not valid (OpenSSO)
---------------------------------------------------------------------------
Key: GTNPORTAL-1027
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1027
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Environment: GateIn trunk (revision 2480) deployed on EAP 5, running on localhost:8080
SSO module trunk (revision 2480),
OpenSSO 8 update 1 deployed on Tomcat (localhost:8888),
Sun Java 1.6
Reporter: Marek Posolda
I have integration with GateIn+JBoss and OpenSSO. GateIn is on localhost:8080 and OpenSSO on Tomcat on localhost:8888. I have session-timeout configured to be only 1 minute instead of default 30 minutes in gatein.ear/02portalwar/WEB-INF/web.xml/ Now going through this scenario:
1) Login as root into GateIn via OpenSSO console
2) Wait some time (2 minutes) until HTTP session in GateIn expire.
3) Restart Tomcat with OpenSSO (or wait bigger amount of time until OpenSSO ticket expires - 2 hours)
4) Go to http://localhost:8080/portal/private/classic. Now I am redirected to blank screen and I am seeing the exception in server log: "java.lang.IllegalStateException: OpenSSO Token is not valid!!". Full stacktrace is in attachement. I am redirected to OpenSSO console after manual removation of cookie iPlanetDirectoryPro from my browser.
I think that if validation of SSO ticket fails, then SSO cookie should be removed from browser and user should be redirected to SSO console? I believe it's more correct than redirecting user to blank screen.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (GTNPORTAL-863) normal window states not being properly updated with render urls
by Matt Wringe (JIRA)
normal window states not being properly updated with render urls
----------------------------------------------------------------
Key: GTNPORTAL-863
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-863
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: PC integration
Reporter: Matt Wringe
Assignee: Matt Wringe
When creating a render url, we are leaving out the normal windows state property from the url in an attempt to simplify the url (assume that the normal mode is the default mode and therefore doesn't necessarily need to be specified in the url).
There appears to be some issues with the integration through. Parts of the portal code itself seems to be setup to assume that no window state means that the window state shouldn't change from the current windowState. This is causing some issues.
The remote portlet will not return the parent window back to the normal mode because of this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years