OpenSAML user discussion

[anshuk pal chaudhuri <>]

Scott,

This is the complete SOAP Request Envelope.

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soapenv:Header>
<wsse:Security soapenv:mustUnderstand="1"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>
<Assertion
AssertionID="d11ef9b473994017e6b1cf59cf19b4e2"
IssueInstant="2005-11-11T04:49:29Z" Issuer="Anshuk"
MajorVersion="1" MinorVersion="1"
xmlns="urn:oasis:names:tc:SAML:1.0:assertion"
xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"
xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol"><Conditions
NotBefore="2005-11-11T04:49:29Z"
NotOnOrAfter="2005-11-11T04:49:29Z"/><AuthenticationStatement
AuthenticationInstant="2005-11-11T04:49:29Z"
AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified"><Subject
xmlns="urn:oasis:names:tc:SAML:1.0:assertion"><NameIdentifier>Anshuk</NameIdentifier></Subject></AuthenticationStatement></Assertion></wsse:Security></soapenv:Header>
 <soapenv:Body>
  <calculateAddition>
   <FirstNum>69</FirstNum>
   <SecondNum>45</SecondNum>
  </calculateAddition>
 </soapenv:Body>
</soapenv:Envelope>

And this is the way I am getting the SAML Assertion
from the SOAPEnvelope.....
 SOAPHeader header = requestEnvelope.getHeader();
                        SOAPHeaderElement soapHeaderElement=
(SOAPHeaderElement)header.extractAllHeaderElements().next();
                        Element samlAssertionElement =
(Element)soapHeaderElement.getChildElements().next();

AND THEN.....................
SAMLAssertion assertion = new
SAMLAssertion(samlAssertionElement);

I am printing the SAML Assetion...Its printing the
assertion also.

Regards,
Anshuk
--- Scott Cantor 
<>
 wrote:

> > I have given the assertion.
> > I think the assertion is fine.
> 
> It's not the XML, it's the code that's finding the
> assertion in the message.
> You're probably on the wrong element.
> 
> > The point you made about the toggling on the
> > strict-dom-checking config property,how do I do
> that?
> 
> SAMLConfig.setProperty, but it's just going to help
> find the bug. Just
> eyeball the SOAP processing code and figure out
> where you're off in some
> way. My guess is from your code that it's actually
> accessing the first child
> of the assertion itself and passing that in, but you
> didn't show the SOAP
> message.
> 
> BTW, attaching SAML assertions to SOAP pretty much
> involves using WSS
> headers. It's not something you just stick in a
> header by itself.
> 
> -- Scott
> 
> 



                
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com