Using this CAS client 2.1.0 release candidate in uPortal.

This evolution of the CAS Java client came into being as a client for use in the YaleInfo Portal for Fall 2004. The YaleCasContext security context could not accomodate a dynamic parameter on the Login URL (providing the uP_fname of a channel to be displayed in focus mode immediately after login) and so did not meet immediate requirements. There are a number of ways to solve this problem; the way we ran with was using a CAS client filter to do the actual ticket validation and a YaleCasFilteredContext, to replace the YaleCasContext security context, as a consumer of the results of authentication, which are exposed by StaticCasReceiptCacherFilter as a CASReceipt.

Here is provided some example source code which uses this CASClient to accomplish these goals.