Its not that it won't work its just that there's additional stuff that must be done because the default filter's storage method is a hashmap-backed storage which isn't distributed. You'd have to implement a storage method that spans the entire cluster.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Thu, Aug 28, 2008 at 1:05 PM, Troy Bull <[EMAIL PROTECTED]> wrote: > On Thu, Aug 28, 2008 at 11:20 AM, Scott Battaglia > <[EMAIL PROTECTED]> wrote: > > > > I'm sorry are you talking about the CAS software using the Weblogic > cluster > > or the client applications being clustered? If its the client > applications > > in the WebLogic cluster there may be an issue with the default backing > for > > the single sign out assuming one server. You would need a storage > mechanism > > for the clustering. > > > > With regards to the callbacks in the logs, is one logout request > generating > > 3 callbacks? If so are they from the same machine? > > > > -Scott > > > Both CAS and the client apps are clustered. The ticket registry for > CAS is maintained with the method from the wiki. > > If this isnt going to work because the apps are clustered knowing that > would be great. Sorry I am so dense. > > troy > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
