ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <>
Subject [jira] [Resolved] (WSS-486) Streaming code does not process a (non-secured) SOAP Fault correctly
Date Mon, 13 Jan 2014 16:42:51 GMT


Colm O hEigeartaigh resolved WSS-486.

    Resolution: Fixed

> Streaming code does not process a (non-secured) SOAP Fault correctly
> --------------------------------------------------------------------
>                 Key: WSS-486
>                 URL:
>             Project: WSS4J
>          Issue Type: Bug
>            Reporter: Colm O hEigeartaigh
>            Assignee: Marc Giger
>             Fix For: 2.0.0
> The streaming code does not process a non-secured SOAP Fault correctly. I've merged some
code to the PolicyEnforcer to not throw a PolicyValidationException when we are an initiator
+ there is no security header + there is no SOAP Fault. This allows a client to see what the
actual error message is, rather than complain about an insecured response.
> However, there is a bug in the SecurityHeaderInputProcessor, it throws the following
> Caused by: org.apache.wss4j.common.ext.WSSecurityException: Request is not a valid SOAP
>         at org.apache.wss4j.stax.impl.processor.input.SecurityHeaderInputProcessor.processNextEvent(
> I can only reproduce in conjunction with CXF. See the following test ("testSOAPFaultError"):

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message