You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "todd wolff (JIRA)" <ji...@apache.org> on 2010/01/15 23:28:54 UTC

[jira] Updated: (WSS-223) Incorrect xpath set on WSDataRef when decrypting an EncryptedHeader instance.

     [ https://issues.apache.org/jira/browse/WSS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

todd wolff updated WSS-223:
---------------------------

    Description: 
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 decrypted parts within PolicyBasedResultsValidator.  Simple one line fix:

Within ReferenceListProcessor.decryptEncryptedData() method, the following line:

dataRef.setXpath(getXPath(decryptedHeader));

should be:

dataRef.setXpath(getXPath(decryptedHeaderClone));

  was:
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);


> 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 decrypted parts within PolicyBasedResultsValidator.  Simple one line fix:
> Within ReferenceListProcessor.decryptEncryptedData() method, the following line:
> dataRef.setXpath(getXPath(decryptedHeader));
> should be:
> dataRef.setXpath(getXPath(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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org