You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Jeff Davis (JIRA)" <ji...@apache.org> on 2008/06/09 22:16:44 UTC
[jira] Created: (SYNAPSE-354) WS-Security should not, by default,
WS-Addressing
WS-Security should not, by default, 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
Priority: Minor
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
[jira] Commented: (SYNAPSE-354) WS-Security should not, by default,
add WS-Addressing
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609795#action_12609795 ]
Ruwan Linton commented on SYNAPSE-354:
--------------------------------------
Now you can engage only ws-Security to the outbound message which will not engage addressing by default. If you need addressing to be engaged this has to be stated separately using both <enableSec/> and <enableAddressing/> tags.
> 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
[jira] Resolved: (SYNAPSE-354) WS-Security should not, by default,
add WS-Addressing
Posted by "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
[jira] Assigned: (SYNAPSE-354) WS-Security should not, by default,
add WS-Addressing
Posted by "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 reassigned SYNAPSE-354:
------------------------------------
Assignee: Ruwan Linton
> 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
>
> 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
[jira] Updated: (SYNAPSE-354) WS-Security should not, by default,
add WS-Addressing
Posted by "Jeff Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Davis updated SYNAPSE-354:
-------------------------------
Summary: WS-Security should not, by default, add WS-Addressing (was: WS-Security should not, by default, WS-Addressing)
> 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
> Priority: Minor
>
> 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