Clustering CAS - why tomcat session replication?

[Ina Müller]

Hello,

we want to use CAS in a HA solution, so I had a look at 
http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS.

It describes three steps:
1.- Ticket Uniqueness
2.- Tomcat Session Replication
3.- Ticket Cache Replication

Steps 1 and 3 are clear. But for what scenario do I need step 2?
What CAS specific stuff in session state has to be replicated?
Isn't it enough to distribute the TGTs among the CAS servers to have a failover solution?

Or lets restate the question:  if I omit step 2, what can go wrong in case of failover to another server?

Thank you for your help, Ina
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6084 bytes
Desc: S/MIME Cryptographic Signature
Url : http://tp.its.yale.edu/pipermail/cas/attachments/20080305/608149bc/attachment.bin