wsit
  1. wsit
  2. WSIT-1439

[Regression]No elements exist with Id/WsuId: uuid_175da065-4d65-40ca-9128-a9fb32adeb51

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: current
    • Fix Version/s: not determined
    • Component/s: security
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      Metro Build: 2.0.1
      Scenario Description:SymmetricBinding with x509 token as SignatureToken and
      EncryptionToken.Also uses SignedEndorsingSupportingTokens and
      DisableStreamingSecurity.

      Exception:
      SEVERE: WSS1316: Sign operation failed.
      javax.xml.crypto.dsig.XMLSignatureException:
      javax.xml.crypto.URIReferenceException: No elements exist with Id/WsuId:
      uuid_175da065-4d65-40ca-9128-a9fb32adeb51
      at org.jcp.xml.dsig.internal.dom.DOMReference.dereference(DOMReference.java:352)
      at org.jcp.xml.dsig.internal.dom.DOMReference.digest(DOMReference.java:278)
      at
      org.jcp.xml.dsig.internal.dom.DOMXMLSignature.digestReference(DOMXMLSignature.java:447)
      at org.jcp.xml.dsig.internal.dom.DOMXMLSignature.sign(DOMXMLSignature.java:343)
      at com.sun.xml.wss.impl.dsig.SignatureProcessor.sign(SignatureProcessor.java:730)
      at com.sun.xml.wss.impl.filter.SignatureFilter.sign(SignatureFilter.java:633)
      at com.sun.xml.wss.impl.filter.SignatureFilter.process(SignatureFilter.java:589)
      at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:93)
      at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:272)
      at
      com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:189)
      at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:150)
      at
      com.sun.xml.wss.jaxws.impl.SecurityTubeBase.secureOutboundMessage(SecurityTubeBase.java:376)
      at
      com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientRequestPacket(SecurityClientTube.java:301)
      at
      com.sun.xml.wss.jaxws.impl.SecurityClientTube.processRequest(SecurityClientTube.java:233)
      at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:629)
      at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:588)
      at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:573)
      at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:470)
      at com.sun.xml.ws.client.Stub.process(Stub.java:319)
      at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:157)
      at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
      at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
      at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:140)
      at $Proxy39.ping(Unknown Source)

      1. PingServices76.wsdl
        9 kB
        msreekanth
      2. soap-log-s76.log
        15 kB
        msreekanth

        Activity

        Hide
        msreekanth added a comment -

        Created an attachment (id=1182)
        webservice policy file

        Show
        msreekanth added a comment - Created an attachment (id=1182) webservice policy file
        Hide
        msreekanth added a comment -

        Created an attachment (id=1183)
        soap log

        Show
        msreekanth added a comment - Created an attachment (id=1183) soap log
        Hide
        msreekanth added a comment -

        Kumar sent an email to Martin asking for a waiver as this may not be a
        showstopped bug for metro 2.0.1 for release.Here is the reason from Kumar:
        1. Firstly becuase this is Non-Optimized legacy security
        2. I belive the change i made in SecurityPolicy code of Metro while fixing 1424
        and the SAML-Interop issue are correct and that the Non-Optimized security code
        needs to be updated to handle this change. I need to investigate more on this.

        Show
        msreekanth added a comment - Kumar sent an email to Martin asking for a waiver as this may not be a showstopped bug for metro 2.0.1 for release.Here is the reason from Kumar: 1. Firstly becuase this is Non-Optimized legacy security 2. I belive the change i made in SecurityPolicy code of Metro while fixing 1424 and the SAML-Interop issue are correct and that the Non-Optimized security code needs to be updated to handle this change. I need to investigate more on this.
        Hide
        msreekanth added a comment -

        4 test cases are failing in the test workspace.s76,s77,s78,s79.

        Show
        msreekanth added a comment - 4 test cases are failing in the test workspace.s76,s77,s78,s79.
        Hide
        m_potociar added a comment -

        Removing waiver for reevaluation since the issue is rather old and no comment
        explains why the issue should be waived for Metro 2.1

        Also, reassigning to the component owner.

        Show
        m_potociar added a comment - Removing waiver for reevaluation since the issue is rather old and no comment explains why the issue should be waived for Metro 2.1 Also, reassigning to the component owner.
        Hide
        kumarjayanti added a comment -

        I belive the change i made in SecurityPolicy code of Metro while fixing 1424
        and the SAML-Interop issue are correct and that the Non-Optimized security code
        needs to be updated to handle this change.

        Show
        kumarjayanti added a comment - I belive the change i made in SecurityPolicy code of Metro while fixing 1424 and the SAML-Interop issue are correct and that the Non-Optimized security code needs to be updated to handle this change.
        Hide
        Sreekanth added a comment -

        WsSecurity SQE functional tests s76,s77,s78,79 are failing due to this.

        Show
        Sreekanth added a comment - WsSecurity SQE functional tests s76,s77,s78,79 are failing due to this.
        Hide
        symonchang added a comment -

        In Metro, the default is use Streaming Security. Use of DisableStreamingSecurity in policy is not recommended. The same issue has been fixed in Streaming Security mode. Marking to 'metro2_3-waiver-request', as the workaround is available.

        Show
        symonchang added a comment - In Metro, the default is use Streaming Security. Use of DisableStreamingSecurity in policy is not recommended. The same issue has been fixed in Streaming Security mode. Marking to 'metro2_3-waiver-request', as the workaround is available.

          People

          • Assignee:
            symonchang
            Reporter:
            msreekanth
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: