Add WS-Addressing to a security configuration
The WS-Addressing specification provides transport-neutral mechanisms that enable SOAP-based web services to communicate addressing information. You can use WSDL security algorithms to add WS-Addressing to your service tests.
Before adding WS-Addressing to a security configuration, you must have a service test with requests and responses related to a valid WSDL.
To add WS-Addressing to a WSDL security algorithm:
- Open the test, select a service request, and in the Raw Transaction Data view, select Enable the display of the XML document after the security processing.
- On the Request Stack page, click...
To edit separate security or processing algorithms for incoming responses, click Show Response Stack to add a Response Stack page to the editor. The WSDL security editor opens.
- Select the Algorithm Stacks page of the WSDL security editor, and in the Security Algorithm list, select or create a security algorithm.
- In the Stack Contents list, click Add > WS-Addressing and specify the settings that are implemented by the service.
- WS-Addressing Algorithm
- Use this block if your service uses either WS-Addressing 2004/08 or the WS-Addressing 1.0 Core standard.
- Namespace
- Specify the namespace for either WS-Addressing 2004/08 or WS-Addressing 1.0 Core.
- Action if request uses WS-Addressing
- Select the action to complete if WS-Addressing is already in the request.
- Replace anonymous address in Reply-to with:
- Select this option to generate the specified address in the Reply-to header instead of an anonymous address.
- Remove WS-Addressing from response
- Select this option to strip any WS-Addressing headers from the response.
- Save the WSDL security algorithm, and select the test editor. The WS-Addressing namespace and header XML content is displayed in the Raw Transaction Data view.
Related:
WSDL security editor overview
Create security profiles for WSDL files
Use a security policy
Implementing a custom security algorithm
Create security profiles for WSDL files
Implementing a custom security algorithm
Related reference:
WSDL security editor reference
Error 404 - Not Found Error 404 - Not Found
The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.