We use terracotta https://wiki.jasig.org/display/CASUM/Terracotta here for HA
as we can share with Shibboleth idp, it give more sense my 2 cents fred On Sun, Jan 15, 2012 at 18:30, Andrew Morgan <[email protected]> wrote: > On Sun, 15 Jan 2012, Fernando Correa wrote: > > Hi to everyone. >> >> I'm looking to implement CAS working in a HA environment. It looks like >> memcached is a simple solution to provide this. I read a lot about it and I >> have some doubts. >> >> 1) If a node fails, we still need to work with another one, without >> authenticate users agains. Is repcached the solution for this? >> > > We use repcached here for that reason. > > > 2) I made a little test with this. I generated some STs from node 1 >> (ST-1, ST-2, ...). I stopped node 1, and I generated some STs from node 2. >> The nodes where named ST-1, ST-2, .... Every node names their tickets in >> that way (ST-1, ST-2, ...)? >> > > Each node makes tickets that begin with ST-###. You should also set the > host.name property in your cas.properties file. Service Tickets will get > the name appended then, for uniqueness (ST-###-abc123-hostname). > > > 3) With memcached in the middle, could I see the tickets stats in the >> console (both nodes will show the same information)? >> > > I'm not sure what you mean. If you have a way to view the memcache cache, > then you should see all of the tickets. > > > 4) Do I have to change something in the client when I used this solution? >> > > Nope. CAS clients work the same as usual. > > Andy > > > -- > 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<http://www.ja-sig.org/wiki/display/JSG/cas-user> > -- 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
