Somewhat arbitrarily, we're calling the new, filtered version of the uPortal CAS Security Provider package version 3.x. This client still works with CAS 2.x. Sorry for the confusion on the version numbers: the version number here refers to the version of this client, not to the version of CAS server upon which it relies.
Motivation
Distribution
Feeling overwhelmed?
There's a lot of documentation here, and I hope that it will be helpful. Note that this site is searchable (see search tool at upper right). However, you may be looking for the no frills guide to installing CAS authentication for uPortal login.
Framework
The new CasConnectionContext looks for an authenticated IYaleCasContext and uses it to provide CAS proxy ticket services to channels. No matter which security context implementation you use, this LocalConnectionContext extension and interface are the mechanisms whereby your code accesses CAS client functionality from within uPortal.
Security Context implementations
Two implementations of IYaleCasContext are provided.
A filtered approach
The YaleCasFilteredContext is a security context implementation which delegates responsibility for participation in the actual CAS tapdance to CASValidateFilter and simply examines and consumes the results. This is the hip, modern, preferred implementation.
A traditional approach
For a more traditional implementation which validates the service ticket inside the SecurityContext itself, use YaleCasContext.