[
https://issues.apache.org/jira/browse/RAMPART-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542363
]
Nandana Mihindukulasooriya commented on RAMPART-110:
----------------------------------------------------
Yes, this happens when there is a Signature element in the security header with
no reference elements. This happens when we try to initiate a XMLSignature with
that signature element.
2007-11-09 11:58:24 (axis2_test.log) org.w3c.dom.DOMException: Cannot
find Reference in Manifest
2007-11-09 11:58:24 (axis2_test.log) at
org.apache.xml.security.signature.Manifest.<init>(Unknown Source)
2007-11-09 11:58:24 (axis2_test.log) at
org.apache.xml.security.signature.SignedInfo.<init>(Unknown Source)
2007-11-09 11:58:24 (axis2_test.log) at
org.apache.xml.security.signature.XMLSignature.<init>(Unknown Source)
This can be avoided within Rampart by not generating signature element at all
if there is nothing to sign. There are 4 cases where we generate signature.
Symmetric binding sign before encrypt, Symmetric binding encrypt before sign,
Asymmetric binding sign before encrypt and Asymmetric binding encrypt before
sign.
> Symmetric binding scenario: "Cannot find Reference in Manifest" Exception is
> thrown
> -----------------------------------------------------------------------------------
>
> Key: RAMPART-110
> URL: https://issues.apache.org/jira/browse/RAMPART-110
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Environment: Axis2 1.3, Rampart 1.3 release
> Reporter: Dobri Kitipov
> Assignee: Nandana Mihindukulasooriya
> Attachments: services.xml, SOAP_Req.xml
>
>
> My understanding is that the problem occurs when there is an empty reference
> list into the signature element in the message.
> I am applying the services.xml and the SOAP request for reference.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
