That was clarifying indeed, Marvin. I am almost positive that it is a network issue so I will look into it.
Thanks for your help, I will keep you posted. It might take me a couple of days, though. 2012/12/4 Marvin Addison <[email protected]> > > If you notice something wrong at a first glance, let me know please. > > I don't see any problems. > > > Could Guice be somehow messing with CAS client? > > Doubtful, but I have no experience with Guice so my opinion is not > very meaningful. > > > About the network environment, I'm not really responsible for it > currently, > > could you give a hint of where to look? > > I mean, what could possibly cause single sign out to fail when single > sign > > on works? > > Because the communication is sourced differently. For single sign-on, > the source of the communication is the client browser. If you're in a > load-balanced environment, the communication likely passes through the > LB to both CAS server and CAS clients. For single sign-out > communication, the source is the CAS server. That would count as > back-channel communication and in many environments does not traverse > the same network path as front-channel communication. You'll have to > evaluate your network environment for further analysis, but hopefully > that brief discussion helps clarify that the communication is > fundamentally different. > > M > > -- > 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
