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

CryptoCoverageChecker prevents handling of SOAPFault-Responses

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.6
    • Fix Version/s: 2.6.8, 2.7.5, 2.5.11
    • Component/s: WS-* Components
    • Labels:
      None
    • Environment:

      JBoss EAP 6

    • Estimated Complexity:
      Unknown

      Description

      Using CXF 2.4.6 in JBoss EAP 6, I'm securing my web services with WS-Security (no WS-SecurityPolicy as the algorithm suite is not supported there).

      For this, I have configured WSS4JInInterceptors and WSS4JOutInterceptors on both client and server, and the setup works.

      To check if incoming messages are signed, encrypted, and with timestamp token, I also have configured a CryptoCoverageChecker on both client and server. Now I have the problem that I cannot obtain Fault answers from the server on the client any more because the CryptoCoverageChecker kicks in and I don't have a chance to access the SOAPFaultException from the server. The server doesn't sign and encrypt Fault answers (which is ok, and this is the case also when using easy WS-SecurityPolicy configurations).

        Activity

        Hide
        coheigea Colm O hEigeartaigh added a comment -


        This is now fixed. I have added a boolean configuration property to CryptoCoverageChecker ("checkFaults"). When this is true (default behaviour) it checks the response Fault for the Crypto requirements. To not check Faults, then set it to false.

        Show
        coheigea Colm O hEigeartaigh added a comment - This is now fixed. I have added a boolean configuration property to CryptoCoverageChecker ("checkFaults"). When this is true (default behaviour) it checks the response Fault for the Crypto requirements. To not check Faults, then set it to false.

          People

          • Assignee:
            coheigea Colm O hEigeartaigh
            Reporter:
            dlatt Dirk Lattermann
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development