I will pass that along. I think we've gotten past our certificate problems, though.
Thanks! Geoff -----Original Message----- From: Joachim Fritschi [mailto:[email protected]] Sent: Wednesday, May 1, 2013 3:25 PM To: [email protected] Subject: Re: [cas-user] CAS Server Sending Empty Response Body Please also have them disable the certificate validation for testing with: phpCAS::setNoCasServerValidation(); Only if this works you should start working with server certifcate validation. Sometimes a broken certificate file will trip up phpCAS and can result in empty queries and curl errors. Regards, Joachim On 01.05.2013 14:06, Whittaker, Geoffrey wrote: > Thank you. > > I'll have them update their path-to-cas field and see if that corrects > the issue. > > Geoff > > *From:*Marvin Addison [mailto:[email protected]] > *Sent:* Tuesday, April 30, 2013 9:09 PM > *To:* [email protected] > *Subject:* Re: [cas-user] CAS Server Sending Empty Response Body > > > Does this log reveal the silver bullet that I just don't see? > > I see a pretty clear sign of a client config problem that would > explain the behavior. > > FD8A .| | | => > > CAS_Client::_readURL('https://myserver.mydomain.unf.edu/login/samlValidate?TARGET=https%3A%2F%2Fflorida.erezlife.com%2Funf_staging%2Fone.php%3Foutputter%3DloginManager%26purpose%3Dlogin', > NULL, NULL, NULL) [Client.php:1748] > > Note the validate URI, login/samlValidate, which is almost certainly wrong. > > FD8A .| | | | => CAS_Client::_buildSAMLPayload() > [Client.php:2432] > FD8A .| | | | <= '<SOAP-ENV:Envelope > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";><SOAP-ENV:Header/><SOAP-ENV:Body><samlp:Request > xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol" MajorVersion="1" > MinorVersion="1" RequestID="_192.168.16.51.1024506224022" > > IssueInstant="2002-06-19T17:03:44.022Z"><samlp:AssertionArtifact>ST-2-rfP6EGq4tZpwUyVgSYnf-myserver.mydomain.unf.edu > > <http://ST-2-rfP6EGq4tZpwUyVgSYnf-myserver.mydomain.unf.edu></samlp:AssertionArtifact></samlp:Request></SOAP-ENV:Body></SOAP-ENV:Envelope>' > FD8A .| | | | => CAS_Request_CurlRequest::sendRequest() > [AbstractRequest.php:218] > FD8A .| | | | | CURL: Set CURLOPT_CAINFO > [CurlRequest.php:123] > FD8A .| | | | | Response Body: > FD8A .| | | | | > <Should have attributes here> > FD8A .| | | | | [CurlRequest.php:82 > > No response at all. Makes sense, CAS issues a 302 redirect (empty > body) for a 404 file not found, which appears to be the case in light > of the URL above. > > M > > -- > You are currently subscribed [email protected] > <mailto:[email protected]> as:[email protected] > <mailto:[email protected]> To unsubscribe, change settings or > access archives, seehttp://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 -- 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
