Uploaded image for project: 'WSS4J'
  1. WSS4J
  2. WSS-223

Incorrect xpath set on WSDataRef when decrypting an EncryptedHeader instance.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.8
    • Fix Version/s: 1.5.9, 1.6
    • Component/s: None
    • Labels:
      None

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

        Attachments

          Activity

            People

            • Assignee:
              coheigea Colm O hEigeartaigh
              Reporter:
              wolfftw todd wolff
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: