This page is for collaborating upon the content of the CAS 3 JA-SIG pre-conference seminar.
Seminar description
This session will introduce what CAS is, what it is trying to accomplish, its architecture and ticket concepts. It will then turn to deployment considerations, progressing from a simple introduction to deploying CAS 3 and configuring a service to use it for authentication ("CASifying an application") through branding CAS and taking advantage of some of the extension points and Spring configuration architecture introduced in CAS 3.
The content of the pre-conference seminar intersects with that of the CAS for Deployers pages. For the moment, many of the links below go to pages also linked from CAS for Deployers. This page should reflect what we're trying to cover in the pre-conference seminar, whereas CAS for Deployers can accomodate additional information.
Introduction
Introduction
What is and why is CAS? Abstractly, what is CAS trying to accomplish? The broad architecture of the service.
Using CAS
Deploying
Where to get CAS. The fact that CAS is free and opensource. How to configure SSL so that you can try out your deployed CAS.
CASifying your first application
Making a JSP page use CAS for authentication using the CASFilter. The CAS user experience.
Introduction to Customizing CAS
Skinning and branding CAS. Plugging in an authentication handler specific to your institution's authentication strategy.
Proxy Tickets
Using CAS with uPortal. And of course proxy tickets are useful even outside of portals.
CAS Clients
Acegi, PhPCas, CAS perl modules, oh my! The rich array of available CAS clients. Features of the CAS protocol that CAS clients can use to provide more compelling user experiences - renew, gateway, logout.
The Cutting Edge: extending CAS 3
Clustering
Clustering CAS3 for performance, for failover, and for fun.
Service Registries
Restricting CAS to only authenticate to recognized services and customizing the UI based on the service the user is trying to access.
Alternate protocol views and user attributes
A SAML ticket validation response view. Extending the ticket validation response to contain user attributes.
Conclusions and where to find more
The CAS Community
Wikis, email discussion lists, the Java Architectures Special Interest Group.