Overview
Integration Server provides predefined policies based on WS-SecurityPolicy and also a set of predefined policies that you can use with the Integration Server WS-Security facility. The main differences in the policies are listed in the table below.
Policies based on WS-SecurityPolicy | WS-Security Facility Policies |
![*](chapterTOC_bullet.png) The policies work with the WS-SecurityPolicy 1.2 standard. | ![*](chapterTOC_bullet.png) The policies are a proprietary format. |
![*](chapterTOC_bullet.png) You can attach the same policy to both consumer and provider web service descriptors. | ![*](chapterTOC_bullet.png) A policy is specific to either a consumer web service descriptor or a provider web service descriptor. |
![*](chapterTOC_bullet.png) The policies support using SAML authentication by including a standard SAML token. | ![*](chapterTOC_bullet.png) WS-Security facility does not support SAML authentication. |
![*](chapterTOC_bullet.png) The policies enforce signing the Timestamp tokens that are added to the security header. | ![*](chapterTOC_bullet.png) The policies did not require that the Timestamp tokens be signed. |
The sections that follow compare the out-of-the-box WS-SecurityPolicy policies with the out-of-the-box WS-Security facility policies.
Note:
The WS-Security facility is deprecated as of Integration Server 10.4 because the web services implementation with which the WS-Security facility is used is deprecated. Specifically, the web services implementation introduced in Integration Server version 7.1 is deprecated.