If you want to merely see the response you can just generate and validate a ticket via the web browser. (enabling DEBUG at the Tomcat level will also show you what Tomcat is writing out to the response)
If you want to see directly what phpCAS is receiving, you may need to enable more logging phpCAS (not sure if that's possible) or add some statements to log it yourself. -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Mon, Dec 15, 2008 at 7:43 PM, Kim Cary <[email protected]> wrote: > We're using CAS 3.3.x and one of our vendors is stating that 'you must > be using the old version since our SAX subsystem is complaining about > malformed response'. > > Just because SAX spits its skull out doesn't necessarily imply we're > not sending XML. > > I can't empirically verify this since turning on debug on our test > server doesn't seem to spit out the XML it returns (though it > dutifully records the test id & pw). > > My test client is phpCAS (sorry I'm so lame as to be stuck with one > client) and phpcase specifies 2.0 when it talks to the server. As > wonderful as the debug output is with PHPCAS, it is not using the > CAS3.0 XML object. > > I can't capture the XML on the server side, apart from the lack of a > suitable client, because its all https, and I get a very nice pcap > file full of ssl encoded data. > > Hit me with the cluebat folks. > > Thanks! > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
