CAS 3.1, global logout, and firewalls

[Lucas Rockwell]

Hi all,

I just learned, via a problem with a slow logout, that CAS holds up  
the logout process until it can either 1) contact all of the services  
that the user logged into, or 2) times out trying to contact the  
services. In other words, a service that is using CAS is running on a  
server that blocks traffic from our CAS servers, and anyone who uses  
that service has to wait 4 minutes before the logout page renders.

Is this by design, or is there some configuration option I can set to  
tell CAS to run the global logout function in another thread and  
render the logout page regardless? (Of course, long-term I would not  
want to do this, but I need to tell all of our services that they  
need to let our CAS servers through their firewalls.)

Thanks.

-lucas