WS-Addressing policy settings

Use this page to define the appropriate WS-Addressing policy assertions for this policy set.

To view this administrative console page, click Services > Policy sets > Application policy sets > policy_set_name > [Policy] WS-Addressing, when the policy set includes the WS-Addressing policy type.

You can configure the WS-Addressing policy type for both client-side and provider-side policy sets. If you enable WS-Policy, this configuration is communicated between servers and clients that support WS-Policy.

WS-Addressing is mandatory

Specifies whether a WS-Addressing SOAP header is included on messages.

Information	Value
Data type	Check box
Default	Cleared
Range	Cleared WS-Addressing is not mandatory. Servers will not generate a fault if they receive a message that does not contain a WS-Addressing header. Clients might not include WS-Addressing headers in SOAP messages, for example, if WS-Policy is enabled and the server does not specify that WS-Addressing is mandatory. Selected WS-Addressing is mandatory. Servers return a fault if they receive a message that does not contain a WS-Addressing header. Clients always include WS-Addressing headers in SOAP messages.

Messaging style

Specifies the messaging style supported by this policy set.

Use the radio buttons to configure the messaging style.

Select Synchronous and asynchronous to specify that there is no restriction on the targeting of response messages.
Select Synchronous only to specify that response messages must be targeted at the WS-Addressing anonymous URI. You might want to use this messaging style in the following situations:
- The SOAP headers are not signed, and WS-Security is not enabled. Specifying the synchronous message exchange pattern prevents the server sending messages to a third party, thereby preventing the server from potentially taking part in a Denial of Service attack.
- Clients with a NAT device between themselves and the endpoint. In this configuration, non-anonymous URIs cannot be routed. Use this setting to prevent the client from sending a message containing a ReplyTo endpoint reference with a non-anonymous URI.
Select Asynchronous only to specify that response messages must not be targeted at the WS-Addressing anonymous URI. This setting does not mean that all non-anonymous URIs are supported, therefore a server can return a fault if it receives a response endpoint reference that it cannot process. You might want to use this messaging style if the endpoint has a very long-running invocation time, and you do not want to hold the connection open while waiting for a response.

The following table shows how the messaging style options correspond to WS-Policy assertions.

Table 1. WS-Addressing messaging style and WS-Policy. This table provides a mapping between messaging style options and WS-Policy assertions.
Messaging style	WS-Policy mapping
Synchronous and asynchronous	wsam:AnonymousResponses or wsam:NonAnonymousResponses
Synchronous only	wsam:AnonymousResponses
Asynchronous only	wsam:NonAnonymousResponses

Information	Value
Required	No
Data type	Radio button

File name: uwbs_wsspsadd.html