WS-Security policies

In IBM® App Connect Enterprise 13.0.7 (and later versions) you can use WS-Security policies to configure WS-Security on integration servers that use Java 17.

Support has been added for SOAP WS-Security message flows on integration servers that use Java 17. You can continue to use existing WS-Security enabled flows with Java 8, or you can upgrade these integration servers to use Java 17. For information about how to migrate Java 8 integration servers, see Migrating integration servers from Java 8 to Java 17 and Migrating WS-Security policy sets and bindings to Java 17.

You create WS-Security Input and WS-Security Request policies by using the Policy editor in the IBM App Connect Enterprise Toolkit. For information about how to create the policies, see Creating a WS-Security Input policy or WS-Security Request policy (for Java 17 integration servers). For information about the properties that you need to set for these policies, see WS-Security Input policy and WS-Security Request policy.

In addition to creating the WS-Security policies in the Policy editor, you must also configure the WS-Policy file by using the WS-Policy editor. You launch the WS-Policy editor by clicking Configure in the Policy editor when you are creating or editing an WS-Security Input or WS-Security Request policy.

You can enable WS-Security for a SOAPInput, SOAPRequest, or SOAPAsyncRequest node by setting the WS-Security policy property in the WS Extensions tab of the node editor. Use this property to specify the name of the WS-Security Input or WS-Security Request policy that you created in the Policy editor. You can also set these properties in the BAR file, by using the BAR file editor. When you are using Java 17, the Policy Set and Policy Set Bindings node properties and the Consumer/Provider Policy Set and Consumer/Provider Policy Set Bindings message flow properties are not used.

To enable WS-ReliableMessaging with Java 17, you set the Use WS-ReliableMessaging property on the WS Extensions tab of the SOAP Input and SOAP Request nodes. If you require more advanced configuration of WS-ReliableMessaging, you can use a WS-ReliableMessaging policy, which you can create and apply to SOAP Input and SOAP Request nodes.

For information about the differences between configuring WS-Security on Java 8 integration servers and Java 17 integration servers, and for an overview of the WS-Security features that are supported with integration servers that are configured to use Java 17, see Using WS-Security with Java 17.