Versions Compared

Old Version 36

changes.mady.by.user Brian Savage

Saved on

compared with

New Version 37

changes.mady.by.user Brian Savage

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tip
titleRelevant webinar

See also the relevant September 2010 Jasig CAS Community Call, with both slides and audio available, which featured a presentation with a perspective on clustering CAS from Howard Gilbert at Yale University.

Warning

This webinar and some other old resources mention an approach for preserving application login state via a Spring Workflow 1.0 configuration option (Spring 1.0 documentation on this here). Spring Webflow 2.0+ (used in modern versions of CAS) no longer has this feature, meaning this state must be maintained in some other way (such as Tomcat clutering covered in this guide).

Overview

Clustering is essential if your CAS instance is to be "highly available," or HA in manager-speak. Since CAS is a stateful application, there must be a way for each CAS instance to know about what the other CAS instance has done. It would be nice to just use one CAS instance (and one instance on the appropriate hardware can probably easily handle your login needs), but if that instance fails, you do not want all of your users to have to log in again.

...