Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-5741

The properties in the requestContext are not copied into RMClient

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-milestone2, 2.7.11
    • Fix Version/s: 3.0, 2.7.12
    • Component/s: WS-* Components
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      When I tried to put all the security configuration properties in the requestContext and call a service with both RM and security policy enabled(like the service in WSRMWithWSSecurityPolicyTest) :
      bp.getRequestContext().put(SecurityConstants.CALLBACK_HANDLER, new KeystorePasswordCallback());
      bp.getRequestContext().put(SecurityConstants.SIGNATURE_PROPERTIES,, getResource("/META-INF/security-client.properties"));
      ....
      This doesn't work as expected and there is exception thrown:
      Failed to send RM protocol message

      {http://schemas.xmlsoap.org/ws/2005/02/rm}

      CreateSequence.: org.apache.cxf.interceptor.Fault: Security configuration could not be detected. Potential cause: Make sure jaxws:client element with name attribute value matching endpoint port is defined as well as a ws-security.signature.properties element within it.

      After I investigated the code, I saw all these ws-scurity configuration properties are not copied into the new created message by RMClient which initialized by RM interceptor.
      That's the root cause for this failure.

        Attachments

          Activity

            People

            • Assignee:
              ema Jim Ma
              Reporter:
              ema Jim Ma
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: