I believe that the CASReceipt is not serializable (but I could be remembering wrong).
Cheers, Scott On Thu, Jul 9, 2009 at 10:48 AM, David Whitehurst <dlwhitehu...@gmail.com>wrote: > Anyone seen this error coming from doFilter() in the Yale CAS Client? > I'm assuming at this point it's this .. > > // Store the authenticated user in the session > if (session != null) // probably unncessary > session.setAttribute(CAS_FILTER_USER, user); > > I am using third-party application and no source. Also the stack > trace is giving bad line numbers. What worries me is the comment // > probably unnecessary .. Is it unnecessary? CAS server should set > this on authentication (server-side). > > Error: > > java.lang.IllegalArgumentException: setAttribute: Non-serializable > attribute > > > David > > -- > David L. Whitehurst > http://www.capehenrytech.com … Providing software instruction through > a sea of Technology. > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
