Hi, It seems to be a very intensive documentation but things are pretty easy.
First, in order to be able to login into the CAS server, you need to keep your web session (to retrieve the login ticket) : you can do that by session affinity or session replication. Then, you need to store your tickets so that all nodes can access them (not only the node on which you logged in even if you have a session affinity). It means : - for Ehcache and JBoss Cache, you need to configure replication - for BD and Memcached, as you have only one storage, you have nothing to do. Finally, the SSO session is hold by the CASTGC cookie which is set by default on the domain and path of the CAS server : it must be accessible by all nodes. Best regards, Jérôme -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
