I'm working on ensuring that all objects placed in the portal's session
are serializable so that uPortal can support session replication out of
the box. The one remaining hurdle is the
edu.yale.its.tp.cas.client.CASReceipt from CAS client 2.2.0-M2.
Does anyone see a reason why this couldn't be a Serializable object?