CAS 3 JA-SIG pre-conference seminar

Owned by Andrew Petro
Last updated: Jun 04, 2005Version comment
2 min read

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 (30 minutes)

What is and why is CAS? Abstractly, what is CAS trying to accomplish? The broad architecture of the service.

Flying Tickets Act I

CAS "flying ticket" demonstration - conceptual (Drew 10 minutes)

CAS 3 Big Picture

Why CAS3, New Architecture (Susan 10 minutes)

Tickets in Action

CAS "flying ticket" walk through related to concrete CAS 3 implemntation (Howard - 10 minutes)

Using CAS (65 minutes)

Deploying

Where to get CAS. The fact that CAS is free and opensource. Recipes to configure SSL so that you can try out your deployed CAS. (Andy 20 minutes)

CASifying your first application

Making a JSP page use CAS for authentication using the CASFilter. The CAS user experience. Lab exercise to set up CAS Filter. (Andrew 20 minutes)

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. (Andrew 5 minutes)

Introduction to Customizing CAS

Skinning and branding CAS. Plugging in an authentication handler specific to your institution's authentication strategy. Lab exercise. (Drew 20 minutes)

Break (10 minutes)

Proxy Tickets (20 minutes)

To use CAS with uPortal we need proxy tickets. Of course they are useful even outside of portals. Example code provided but no lab exercise.

Flying Tickets Act 2

"flying proxy ticket" demonstration - conceptual (Drew 10 minutes)

Proxy Tickets in Action

Walk through proxy tickets in concrete CAS 3 implementation (Howard - 10 minutes)

The Cutting Edge: extending CAS 3 (45 minutes)

(Howard 45 minutes)

Objects and interfaces

  • Principals
    Now with attributes
  • Authentication
  • views
  • handlers
  • resolvers
  • validators

Clustering

Clustering CAS3 for performance, for failover, and for fun. Ticket Caching component.

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.

Questions (10 minutes)

Conclusions and where to find more

The CAS Community

Wikis, email discussion lists, the Java Architectures Special Interest Group.