Dear Marvin, On Wed, 04 Mar 2009 21:35:43 -0500, Marvin Addison <[email protected]> wrote: > Despite "Success" in the response above, that is actually the payload > returned for a failed ticket validation. See > http://www.middleware.vt.edu/doku.php?id=middleware:cas:client#sample_saml_responses > for examples of successful SAML responses. Note the NameIdentifier > element that contains the NetID.
Ah, OK, understood :-) Thank you so much for the tip and link link :-) > As I mentioned in my previous post, you must send a HTTP POST to > /samlValidate whose body content is a properly formed SAML assertion > wrapped in a SOAP envelope. > >> https://mycasdomainname/cas/samlValidate?TARGET=http://localhost/foo&ticket=ST-1-DvuJvba6fwTP0uydDtuN-cas > > Browsing to the above URL in Firefox will send an HTTP GET request to > /samlValidate, which cannot be understood by the CAS server. You can > certainly play around with CAS SAML support using a simple HTTP client > like curl or wget, but Firefox is probably the wrong tool for that > sort of investigation. Ooops, thanks for the advice, I was not aware that it had to be an http post request. In that case it probably makes sense to use the CAS Client (i.e. for proper testing/validation). Thank you so much, unai -- 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
