Incorrect xpath set on WSDataRef when decrypting an EncryptedHeader instance.
-----------------------------------------------------------------------------
Key: WSS-223
URL: https://issues.apache.org/jira/browse/WSS-223
Project: WSS4J
Issue Type: Bug
Reporter: todd wolff
Assignee: Ruchith Udayanga Fernando
Xpath is calculated using element still attached to EncryptedHeader parent.
The clone, which is attached to soap header should be used instead. As a
result, rampart 1.5-SNAPSHOT fails to validate encrypted parts within
PolicyBasedResultsValidator when validating encrypted parts. Simple one line
fix:
Within ReferenceListProcessor.decryptEncryptedData() method, the following line:
dataRef.setProtectedElement(decryptedHeader);
should be:
dataRef.setProtectedElement(decryptedHeaderClone);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
