We don't use single-log-out, so I'll disable that. Thanks for the quick turnaround!
For anyone searching this in the future, here's how (I found this in a message in the archive): (from Thomas Talbott, 1/18/2011, titled "Re: [cas-user] Ticket expiration triggers logout of all services (CAS-686) - why?") You need to copy "argumentExtractorsConfiguration.xml" to your "spring-configuration" directory and add the property to each extractor: <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:p="http://www.springframework.org/schema/p"; xmlns:util="http://www.springframework.org/schema/util"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-3.0.xsd";<http://www.springframework.org/schema/util/spring-util-3.0.xsd%22>> <description> Argument Extractors are what are used to translate HTTP requests into requests of the appropriate protocol (i.e. CAS, SAML, SAML2, OpenId, etc.). By default CAS and SAML are enabled. </description> <bean id="casArgumentExtractor" class="org.jasig.cas.web.support.CasArgumentExtractor" p:httpClient-ref="httpClient" p:disableSingleSignOut="true"/> <bean id="samlArgumentExtractor" class="org.jasig.cas.web.support.SamlArgumentExtractor" p:httpClient-ref="httpClient" p:disableSingleSignOut="true" /> <util:list id="argumentExtractors"> <ref bean="casArgumentExtractor" /> <ref bean="samlArgumentExtractor" /> </util:list> </beans> :) Tim From: Scott Battaglia [mailto:[email protected]] Sent: Wednesday, May 04, 2011 9:51 AM To: [email protected] Subject: Re: [cas-user] CAS Periodically sending POST requests Its most likely the service logout callbacks. Do you use single log out? If not you can disable it. On Wed, May 4, 2011 at 12:47 PM, Tim McLaughlin <[email protected]<mailto:[email protected]>> wrote: Hello, I've recently upgraded our production CAS from 3.2.x to 3.4.7, and am seeing some odd traffic. Every hour and 24 minutes (approximately) CAS appears to send a large number of POST requests to what looks like every "service" URL it has approved. Our uPortal installation is load-balanced by an F5 BigIP LTM, which has an SSL transaction-per-second limit that is being hit when these POST requests are sent -- only briefly, but hit, nonetheless. I'm wondering if this is a bug, or, if not, which part of the CAS code does the POST requests so that I can tweak the timing for our local install. If it even paused a few millis between sending POSTS it would alleviate the problem we're getting. In any case, I'm just figuring out the symptoms as I go here, so any help finding the right part of the code would be helpful. Thanks, Tim -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[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 -- 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
