[CXF-4954] CryptoCoverageChecker prevents handling of SOAPFault-Responses

• 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

Environment

JBoss EAP 6

• Estimated Complexity: Unknown
• Assignee: Colm O hEigeartaigh
• Reporter: Dirk Lattermann
• Created: 09/Apr/13 14:57
• Updated: 14/Aug/13 15:50
• Resolved: 26/Apr/13 16:11

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