I was just going to add a system property to each server that is a comma delimited list of servers. Like this: Cas.singlesignout.peers=appserver1.utah.edu,appserver2.utah.edu, etc.
Then I was going to extend the CAS single signout filter and have the doFilter() use HttpClient to forward the signout request to all the peers in the list. Of course this does not support dynamically adding servers to the load balancer or reverse proxy. But we don't really do that anyway. To be honest I really despise JMS queues, but I can't really explain why. Bryan Wooten [email protected] Work: 801.585.9323 Cell: 801.414.3593 From: Scott Battaglia [mailto:[email protected]] Sent: Saturday, July 10, 2010 2:30 PM To: [email protected] Subject: Re: [cas-user] useSession=false problem I've considered that solution for re-broadcasting. The ideal situation would be if there's a lightweight library out there that can handle either multicast or unicast messaging via configuration (I'd rather not write one). Otherwise, we can just hook into all of your JMS topics, right? ;-) -- 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
