[
https://issues.apache.org/jira/browse/CXF-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved CXF-4954.
--------------------------------------
Resolution: Fixed
> CryptoCoverageChecker prevents handling of SOAPFault-Responses
> --------------------------------------------------------------
>
> Key: CXF-4954
> URL: https://issues.apache.org/jira/browse/CXF-4954
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.4.6
> Environment: JBoss EAP 6
> Reporter: Dirk Lattermann
> Assignee: Colm O hEigeartaigh
> Fix For: 2.5.11, 2.6.8, 2.7.5
>
>
> 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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
