It might, yes, since the SLO callbacks are synchronous the job will block until something comes out of the operation. Future versions of CAS do support sending async requests out, and perhaps with a little bit of modification you could make your deployment do so...or upgrade to a version that does support this...or as Jérôme says tune the timeout settings to a reasonable degree to reach a balancing point.
> -----Original Message----- > From: Baron Fujimoto [mailto:ba...@hawaii.edu] > Sent: Wednesday, November 5, 2014 11:55 AM > To: cas-user@lists.jasig.org > Subject: Re: [cas-user] SLO: impact of unresolvable hosts? > > Thanks for the advice on tuning the timeout parameters. We expected the > HTTP requests to fail for the unresolvable hosts, but our concern is > whether this would also block servicing subsequent requests from other > "normal" resolvable hosts until the requests for the unresolvable hosts > timed out. > > Aloha, > -baron > > On Tue, Nov 04, 2014 at 08:06:50AM +0100, Jérôme LELEU wrote: > >Hi, > > > >CAS 3.4 is definitely an old CAS server version. The logout process is > >handled by sending HTTP requests from the CAS server using the > >HttpClient > >class: > >https://github.com/Jasig/cas/blob/3.4.x/cas-server-core/src/main/java/o > >rg/jasig/cas/util/HttpClient.java > >. > >If hosts cannot be resolved by your CAS server, requests will fail. In > >that case, you may want to adjust the settings (connectTimeout and > readTimeout). > >Best regards, > > > > > >Jérôme LELEU > >Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj > >Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org > > > >2014-11-04 1:43 GMT+01:00 Baron Fujimoto <ba...@hawaii.edu>: > > > >> We have a client with an application on a private network. They have > >> local DNS set up so that hosts on their private network can resolve > >> the host names of their CAS-protected application hosts. Users not on > >> their private network will not be able to resolve the application > >> server hostnames. We think this should work for their users if the > >> registered service URL is on their private network and resolvable to > >> their users via that networks local DNS. > >> > >> What we are unsure about is whether there may be any detrimental > >> impact on the CAS server (3.4.11) where SLO is concerned. We don't > >> expect SLO to work for them because their application host is > >> unresolvable from our perspective, but could this cause some other > >> type problem (i.e. performance degrading timeouts for unresolvable > >> hosts or some other exception) that would be deleterious to the server > in some non-negligible way? > >> > >> -baron > >> -- > >> Baron Fujimoto <ba...@hawaii.edu> :: UH Information Technology > >> Services minutas cantorum, minutas balorum, minutas carboratum > >> desendus pantorum > >> > >> -- > >> You are currently subscribed to cas-user@lists.jasig.org as: > >> lel...@gmail.com > >> To unsubscribe, change settings or access archives, see > >> http://www.ja-sig.org/wiki/display/JSG/cas-user > >> > > > >-- > >You are currently subscribed to cas-user@lists.jasig.org as: > >ba...@hawaii.edu To unsubscribe, change settings or access archives, > >see http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- > Baron Fujimoto <ba...@hawaii.edu> :: UH Information Technology Services > minutas cantorum, minutas balorum, minutas carboratum desendus pantorum > > -- > You are currently subscribed to cas-user@lists.jasig.org as: > mmoay...@unicon.net To unsubscribe, change settings or access archives, > see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
