Bug 793300 (JBEPP-384) - CAS integration fails in clustered server configuration
Summary: CAS integration fails in clustered server configuration
Keywords:
Status: CLOSED WONTFIX
Alias: JBEPP-384
Product: JBoss Enterprise Portal Platform 4
Classification: JBoss
Component: Portal
Version: 4.3.0.GA_CP4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0.GA_CP7
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-08 12:47 UTC by Martin Weiler
Modified: 2012-01-03 23:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
EPP 4.3 with CAS integrated as documented in the Reference Guide, using the all or production configuration: http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3.CP04/html/Reference_Guide/ch21s03.html
Last Closed: 2011-12-13 17:05:57 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-384 0 None None None Never

Description Martin Weiler 2010-06-08 12:47:03 UTC
Date of First Response: 2010-07-07 09:37:56
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/808593
Workaround Description: Comment or remove the <distributable/> flag from jboss-portal-ha.sar/portal-server.war/WEB-INF/web.xml.
project_key: JBEPP

The redirect to the Portal page after logging in at CAS Authentication Server's login screen fails with the following exception:

2010-06-08 14:37:56,059 ERROR [org.apache.catalina.connector.CoyoteAdapter] An exception or error occurred in the container during the request processing
java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute
	at org.jboss.web.tomcat.service.session.ClusteredSession.setAttribute(ClusteredSession.java:567)
	at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:130)
	at org.jboss.portal.identity.sso.cas.CASAuthenticationValve.invoke(CASAuthenticationValve.java:343)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:595)

edu.yale.its.tp.cas.client.CASReceipt is not serializable in CAS version 3.0.7.

Comment 2 mark yarborough 2011-11-09 22:34:06 UTC
Moved to 43 CP7 for triage after 5.2 ships.

Comment 3 Jared MORGAN 2012-01-03 23:20:14 UTC
Release Notes Docs Status: Added: Not Required



Note You need to log in before you can comment on or make changes to this bug.