Hi, I'm experiencing problems with a low socket timeout value when connecting to a proxy callback URL from CAS.
The scenario is: 1. Client authenticates through CAS web interface 2. Service sends ticket to /proxyValidate on CAS with pgtUrl for proxy callback 3. CAS calls pgtUrl - but does not pass any parameters. 4. CAS connection to pgtUrl times out and CAS continues to validate without providing a proxy ticket pgtUrl is definitely valid, as I can see CAS connects to it from logging, pgtUrl also responds correctly, but CAS has already timed out the connection and moved on before it can get the response back. My understanding of 3. is that CAS may send an empty GET to pgtUrl before following with parameters - so I think this is OK? I've taken a look in the CAS log and can see the following trace: ACTION: SERVICE_TICKET_CREATED APPLICATION: CAS WHEN: Wed Jul 07 13:00:00 BST 201 ============================================================ ERROR [ org.jasig.cas.util.HttpClient] - <Read timed out> java.net.SocketTimeoutException: Read timed out.... I'm assuming I can fix this by upping the timeout value in the cas HttpClient connection - I'm currently building CAS using the maven overlay method - can anyone point me to a spring bean config or similar I can use to up this value, or is there another problem here? Cheers, Russ. -- 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-dev
