[jira] Resolved: (SYNAPSE-354) WS-Security should not, by default, add WS-Addressing

["Ruwan Linton (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SYNAPSE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruwan Linton resolved SYNAPSE-354.
----------------------------------

       Resolution: Fixed
    Fix Version/s: NIGHTLY

Fixed on the svn trunk

> WS-Security should not, by default, add WS-Addressing
> -----------------------------------------------------
>
>                 Key: SYNAPSE-354
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-354
>             Project: Synapse
>          Issue Type: Improvement
>    Affects Versions: 1.2
>            Reporter: Jeff Davis
>            Assignee: Ruwan Linton
>            Priority: Minor
>             Fix For: NIGHTLY
>
>
> When WS-Security is enabled on an outbound message (enableSec), the resulting SOAP header also adds WS-Addressing. This is a problem if the receiving services is not anticipating WS-Addressing, or where it's optional. If the receiving service is not prepared to handle WS-Addressing, the response returned will not contained the necessary WS-Addressing elements, causing a Rampart error. 
> Granted, I am far from an expert on WS-Security and WS-Addressing, but I did read through the WS-Security spec, and don't see any mention that WS-Addressing is required if it is used. If you want both, it seems as though you could indicate as much by specifying both enableSec and enableAddressing specifically.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org