[
https://issues.apache.org/jira/browse/RAMPARTC-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568825#action_12568825
]
Supun Kamburugamuva commented on RAMPARTC-66:
---------------------------------------------
I think the issue is obivious. In the oxs_axiom_deserialize_node method what we
are doing is creating a axiom_stax_builder and creating the node from the
scratch. But this doesn't work since in a case like this some of the namespaces
are not declared in the encrypted node. So instead of creating a
axiom_stax_builder and creating the nodes from the scratch we should use a
axom_data_source.
> decrypted data cannot be deserialized, if namespace is defined in soap
> envelope element
> ---------------------------------------------------------------------------------------
>
> Key: RAMPARTC-66
> URL: https://issues.apache.org/jira/browse/RAMPARTC-66
> Project: Rampart/C
> Issue Type: Bug
> Components: OMXMLSecurity
> Affects Versions: 1.2.0
> Reporter: Lukas JOSEFIK
> Assignee: Glen Daniels
>
> In example below, if content of body is encrypted, then
> oxs_axiom_deserialize_node fails with
> invalid data , Building node failed
> encryption failed , Cannot deserialize a node from the content.
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:x0="http://example.org/x";>
> <SOAP-ENV:Body>
> <m:a xmlns:m="http://example.org/m";>
> <x0:B>
> </x0:B>
> </m:a>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> No problem with following
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
> <SOAP-ENV:Body>
> <m:a xmlns:m="http://example.org/m"; xmlns:x0="http://example.org/x";>
> <x0:B>
> </x0:B>
> </m:a>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
