CAS 3.1, global logout, and firewalls

[Scott Battaglia]

Lucas,

That's a bug. We should have designed it to be configurable.  If you can
open a JIRA issue we can get that addressed for the next release.

Thanks
-Scott

On Dec 12, 2007 2:02 PM, Lucas Rockwell <lr at berkeley.edu> wrote:

> 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
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>



-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20071212/8700ec8b/attachment.html