...
The YaleCasFilteredContext is an IYaleCasContext implementation which consumes the results of the CASValidateFilter having performed the actual authentication.
How does it work?
Maybe you would like to view the source code.
How do I configure it?
You'll need to configure the security context in your security.properties file and configure the CASValidateFilter in your web.xml.
Setting the security.properties
...
In your web.xml, you need to map and configure the CASValidateFilter and a helper filter which provides a static cache so that the YaleCasFilteredContext can obtain the CASReceipt bearing the results of the authentication.
...
The YaleCasFilteredContext is part of the Yale uPortal CAS security provider package, available here.
Proxying authentication
The above instructions should get you to the point where users can authenticate to your uPortal itself using CAS. A killer feature for portals that CAS offers beyond this initial authentication is proxy authentication. In this section we describe the additional configuration you need to make to turn on proxy authentication. We highly recommend that you first verify that you are able to CAS authenticate to your uPortal istself before tackling the additional complexities of proxy authentication.
Receiving proxy tickets
You'll need to map the ProxyTicketReceptor servlet in your web.xml. This servlet must be available via https:
...
Asking for proxy tickets
Having mapped ProxyTicketReceptor, you're prepared to receive proxy tickets if the CAS server would send them to you. But you also need to configure the CASValidateFilter to ask for them.
...