[
https://issues.apache.org/jira/browse/RAMPART-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Vladov updated RAMPART-157:
----------------------------------
Attachment: SignedEncryptedElements.patch
Sure. Here it is.
And hereby I generously grant the ASF whatever license it needs for the patch :D
> Duplicate namespace declaration in SingedEncryptedElements assertion
> --------------------------------------------------------------------
>
> Key: RAMPART-157
> URL: https://issues.apache.org/jira/browse/RAMPART-157
> Project: Rampart
> Issue Type: Bug
> Components: rampart-policy
> Environment: any
> Reporter: Stefan Vladov
> Assignee: Ruchith Udayanga Fernando
> Priority: Minor
> Attachments: SignedEncryptedElements.patch
>
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> The serialize method in org.apache.ws.secpolicy.model.SignedEncryptedElements
> causes duplicate namespace declaration in the assertion. The bug seems to be
> introduced as a result of the bug fix to Rampart issue 123. The problematic
> code is:
> // xmlns:sp=".."
> writer.writeNamespace(prefix, namespaceURI);
> if (writerPrefix == null) {
> // xmlns:sp=".."
> writer.writeNamespace(prefix, namespaceURI);
> }
> Normally the writer prefix won't be null, however if the
> SignedEncryptedElements assertion is the first in the policy and no prior
> declarations of the security policy namespace exist, the writer prefix is
> null and the namespace is declared twice, resulting in an exception when
> parsed afterwards.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
