[
https://issues.apache.org/jira/browse/CXF-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322908#comment-14322908
]
Colm O hEigeartaigh commented on CXF-6255:
------------------------------------------
The warning should ideally be resolved by the remote web service securing the
SOAP Fault, i.e. by adding the WSS4JOutInterceptor to the outbound fault
interceptor chain if configuring via "actions", or else by referencing a policy
in the fault message parts if using WS-SecurityPolicy.
Colm.
> WSS4JInInterceptor: "Security header, but it's a fault"
> -------------------------------------------------------
>
> Key: CXF-6255
> URL: https://issues.apache.org/jira/browse/CXF-6255
> Project: CXF
> Issue Type: Improvement
> Reporter: Richard O'Sullivan
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When CXF processes a SoapFault it logs this WARNing: "Request does not
> contain Security header, but it's a fault.". The message is logged from the
> handleMessage at WSS4JInInterceptor in the package
> org.apache.cxf.ws.security.wss4j.
> The message is cryptic but I think it is intended to be an INFO or DEBUG
> instead of a WARN.
> If I'm correct please make this an INFO or a DEBUG; otherwise, rewrite the
> message to indicate a course of action to eliminate the warning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
