You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Supun Kamburugamuva <su...@gmail.com> on 2008/02/14 08:31:29 UTC
axiom unacceptable behaviour
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 & 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 & 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..
Re: axiom unacceptable behaviour
Posted by Senaka Fernando <se...@wso2.com>.
Hi all,
I have attached the proposed fix to the remainder of this issue, at [1].
This fixes the issues in write_empty_element() methods for Guththila and
some misinterpretations in om_element.c that gave trouble for the empty
element case. Please be kind enough to test it. I used both the axis2.xml,
and the .xml file that Supun provided and I discovered no errors.
Regards,
Senaka
> Hi all,
>
> Changed it back to what it was before. Even Guththila wont work properly
> for that given .xml file. Therefore, need to see the errors caused by the
> write_empty_element() methods. I assumed that they would work fine, and I
> used the axis2.xml as the test case, from which I thought it is bug free.
> Therefore, I apologize for any inconvenience caused.
>
> Regards,
> Senaka
>
>>> Hi Supun,
>>>
>>> On Thu, Feb 14, 2008 at 3:32 PM, Supun Kamburugamuva
>>> <su...@gmail.com>
>>> wrote:
>>>
>>>> +1 for reverting the change since it breaks some of the rampart
>>>> samples. I did re-open the issue.
>>>>
>>>
>>> Can you please revert the change for that issue ? I would like to get
>>> it
>>> done for Axis2/C 1.3.0 RC2
>>
>> OK, I can revert this. However, this was a fix for Guththila
>> specifically,
>> as it has two methods, one to print an empty element and another to
>> print
>> any other element. But, if we don't store that whether the element was
>> empty or not, we can't call the proper method. I bet this was caused by
>> libxml2. In that case the bug is not here. but in the libxml2 wrapper.
>> Please check on that. For the moment, I will therefore, revert this for
>> libxml2 only.
>>
>> Regards,
>> Senaka.
>>
>>>
>>> thanks,
>>> Dinesh
>>>
>>> --
>>> http://nethu.org/
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: axiom unacceptable behaviour
Posted by Senaka Fernando <se...@wso2.com>.
Hi all,
Changed it back to what it was before. Even Guththila wont work properly
for that given .xml file. Therefore, need to see the errors caused by the
write_empty_element() methods. I assumed that they would work fine, and I
used the axis2.xml as the test case, from which I thought it is bug free.
Therefore, I apologize for any inconvenience caused.
Regards,
Senaka
>> Hi Supun,
>>
>> On Thu, Feb 14, 2008 at 3:32 PM, Supun Kamburugamuva <su...@gmail.com>
>> wrote:
>>
>>> +1 for reverting the change since it breaks some of the rampart
>>> samples. I did re-open the issue.
>>>
>>
>> Can you please revert the change for that issue ? I would like to get it
>> done for Axis2/C 1.3.0 RC2
>
> OK, I can revert this. However, this was a fix for Guththila specifically,
> as it has two methods, one to print an empty element and another to print
> any other element. But, if we don't store that whether the element was
> empty or not, we can't call the proper method. I bet this was caused by
> libxml2. In that case the bug is not here. but in the libxml2 wrapper.
> Please check on that. For the moment, I will therefore, revert this for
> libxml2 only.
>
> Regards,
> Senaka.
>
>>
>> thanks,
>> Dinesh
>>
>> --
>> http://nethu.org/
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: axiom unacceptable behaviour
Posted by Senaka Fernando <se...@wso2.com>.
> Hi Supun,
>
> On Thu, Feb 14, 2008 at 3:32 PM, Supun Kamburugamuva <su...@gmail.com>
> wrote:
>
>> +1 for reverting the change since it breaks some of the rampart
>> samples. I did re-open the issue.
>>
>
> Can you please revert the change for that issue ? I would like to get it
> done for Axis2/C 1.3.0 RC2
OK, I can revert this. However, this was a fix for Guththila specifically,
as it has two methods, one to print an empty element and another to print
any other element. But, if we don't store that whether the element was
empty or not, we can't call the proper method. I bet this was caused by
libxml2. In that case the bug is not here. but in the libxml2 wrapper.
Please check on that. For the moment, I will therefore, revert this for
libxml2 only.
Regards,
Senaka.
>
> thanks,
> Dinesh
>
> --
> http://nethu.org/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: axiom unacceptable behaviour
Posted by Dinesh Premalal <xy...@gmail.com>.
Hi Supun,
On Thu, Feb 14, 2008 at 3:32 PM, Supun Kamburugamuva <su...@gmail.com>
wrote:
> +1 for reverting the change since it breaks some of the rampart
> samples. I did re-open the issue.
>
Can you please revert the change for that issue ? I would like to get it
done for Axis2/C 1.3.0 RC2
thanks,
Dinesh
--
http://nethu.org/
Re: axiom unacceptable behaviour
Posted by Supun Kamburugamuva <su...@gmail.com>.
+1 for reverting the change since it breaks some of the rampart
samples. I did re-open the issue.
On 2/14/08, Samisa Abeysinghe <sa...@wso2.com> wrote:
> 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 <su...@gmail.com> 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 & 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 & 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: axis-c-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: axiom unacceptable behaviour
Posted by Samisa Abeysinghe <sa...@wso2.com>.
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 <su...@gmail.com> 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 & 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 & 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: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: axiom unacceptable behaviour
Posted by Supun Kamburugamuva <su...@gmail.com>.
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 <su...@gmail.com> 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 & 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 & 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org