Re: axiom unacceptable behaviour

Thu, 14 Feb 2008 01:11:58 -0800

I tested and yes you are correct, it is broken. Shall we revert this change, re-open issue http://issues.apache.org/jira/browse/AXIS2C-979 and attach your XML there as a test case? 

Thanks,
Samisa...

Supun Kamburugamuva wrote:

Hi again,

I think the misbehavior is due to the changes done to the om_output.c
in the revision 620653.

Regards,
Supun.

On 2/13/08, Supun Kamburugamuva <[EMAIL PROTECTED]> wrote:

Hi All,
 I have the following XML coming from a service (in the wire).

 <wst:RequestSecurityTokenResponse
 xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust";>
  <wst:RequestedSecurityToken>
    <saml:Assertion AssertionID="3c9956ac-defa-494e-be52-9df6b515b1d3"
 IssueInstant="2008-02-14T08:21:31.718Z" MinorVersion="1"
 Issuer="http://ws.apache.org/rampart/c"; MajorVersion="1"
 xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">
      <saml:Conditions NotBefore="2008-02-14T08:21:31.718Z"/>
      <saml:AuthenticationStatement
 AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password"
 AuthenticationInstant="2008-02-14T08:21:31.718Z">
        <saml:Subject>
          <saml:NameIdentifier NameQualifier="University of Moratuwa"
 Format="#emailAddress">Computer Science &amp; Engineering
 Department</saml:NameIdentifier>
          <saml:SubjectConfirmation>
            
<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>
          </saml:SubjectConfirmation>
        </saml:Subject>
        <saml:SubjectLocality DNSAddress="192.148.5.8" IPAddress="128.5.6.4"/>
        <saml:AuthorityBinding
 Location="http://myhome.com/sevices/echo"; Binding="SOAP"
 AuthorityKind="abc:aa:aa"/>
      </saml:AuthenticationStatement>
    </saml:Assertion>
  </wst:RequestedSecurityToken>
  <wst:RequestedProofToken
 xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust";>
    <wst:BinarySecret
 
Type="http://schemas.xmlsoap.org/ws/2005/02/trust/SymmetricKey";>ySe3FZTpubJAGk8Dc/LrCztH1ciwQxHiIijoglrJTn8=</wst:BinarySecret>
  </wst:RequestedProofToken>
 </wst:RequestSecurityTokenResponse>


 But when the axiom is built from this XML and again converted to the
 string form the following XML is there.


 <wst:RequestSecurityTokenResponse
 xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust";>
  <wst:RequestedSecurityToken>
    <saml:Assertion AssertionID="3c9956ac-defa-494e-be52-9df6b515b1d3"
 IssueInstant="2008-02-14T08:21:31.718Z" MinorVersion="1"
 Issuer="http://ws.apache.org/rampart/c"; MajorVersion="1"
 xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">
      <Conditions xmlns="urn:oasis:names:tc:SAML:1.0:assertion"/>
      <Conditions NotBefore="2008-02-14T08:21:31.718Z"/>
      <saml:AuthenticationStatement
 AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password"
 AuthenticationInstant="2008-02-14T08:21:31.718Z">
        <saml:Subject>
          <saml:NameIdentifier NameQualifier="University of Moratuwa"
 Format="#emailAddress">Computer Science &amp; Engineering
 Department</saml:NameIdentifier>
          <saml:SubjectConfirmation>
            
<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>
          </saml:SubjectConfirmation>
        </saml:Subject>
        <SubjectLocality xmlns="urn:oasis:names:tc:SAML:1.0:assertion"/>
        <SubjectLocality DNSAddress="192.148.5.8" IPAddress="128.5.6.4"/>
        <AuthorityBinding xmlns="urn:oasis:names:tc:SAML:1.0:assertion"/>
        <AuthorityBinding Location="http://myhome.com/sevices/echo";
 Binding="SOAP" AuthorityKind="abc:aa:aa"/>
      </saml:AuthenticationStatement>
    </saml:Assertion>
  </wst:RequestedSecurityToken>
  <wst:RequestedProofToken
 xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust";>
    <wst:BinarySecret
 
Type="http://schemas.xmlsoap.org/ws/2005/02/trust/SymmetricKey";>ySe3FZTpubJAGk8Dc/LrCztH1ciwQxHiIijoglrJTn8=</wst:BinarySecret>
  </wst:RequestedProofToken>
 </wst:RequestSecurityTokenResponse>

 This behaviour is totally unacceptable. You can see in the serialized
 XML there are new XML elements created and they are wrong. I have used
 libxml2 as the XML parser. I have attached the XML files as
 attachements. Test.xml –incloming XML and out.xml serialized XML.

 Regards

Supun..




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to