I'd suggest using this webapp: https://github.com/UniconLabs/cas-sample-java-webapp
The trick is, you'd configure this application's web.xml to authenticate via CAS1, and yet validate the service ticket by issuing the request to CAS2. Then, swap. If replication works correctly, you'd be presented with a sample page that shows your id. This works if you just want to test replication. If you'd rather actually examine and interview the cache, then the monitor might be more useful. > -----Original Message----- > From: Laura McCord [mailto:[email protected]] > Sent: Friday, November 15, 2013 1:55 PM > To: [email protected] > Subject: [cas-user] Ehcache Replication > > I think I finally got a replication method working using > EhcacheTicketRegistry. I installed it on a couple development servers that > aren't so constrained by network firewalls so it appears that I have no more > errors. However, how are people monitoring ticket replication? Are you using > Ehcache Monitor? Or is there another method to verify that replication is > happening? > > Thanks, > Laura > > > > -- > 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 -- 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
