Migrate the client-side bindings file

We can migrate the WS-Security client-side binding configuration for a Java EE V1.3 application to a Java EE Version 1.4 application.

The following table lists the mapping of the top-level sections under the client-side Port Bindings tab within a Java EE V1.3 application to a Java EE Version 1.4 application.

Table 1. The mapping of the configuration sections

Java EE V1.3 binding configuration for WS-Security	Java EE V1.4 binding configuration for WS-Security
Security Request Sender Binding Configuration	Security Request Generator Binding Configuration
Security Response Receiver Binding Configuration	Security Response Consumer Binding Configuration

Consider the following steps to migrate the client-side binding configuration from a Java EE V1.3 application to a Java EE Version 1.4 application. These steps are dependent upon the specific configuration. The steps are based on typical scenarios, but the steps are not all-inclusive.

 

• Migrate the information in the Security Request Sender Binding Configuration section in a Java EE V1.3 application to a Java EE Version 1.4 application. The migrations process for the Security Request Sender Binding Configuration section is similar to the process for the Response Sender Binding Configuration Details section in the server-side binding configuration.

  See Migrate the server-side bindings file.

• Migrate the information in the Key Locators, Signing Information, and the Encryption Information sections of the Java EE V1.3 application to a Java EE Version 1.4 application. The migration process for these elements on the client side is similar to migration process on the server side. For more information, see Migrate the server-side bindings file.

• Migrate the information in the Login Bindings section in a Java EE Version 1.3 application to a Java EE V1.4 application. The migration of the Login Bindings section depends upon the value of the authentication method. If the authentication method is BasicAuth or IDAssertion, configure a token generator for the username token. If the authentication method is LTPA, select the com.ibm.wsspi.wssecurity.token.LTPATokenGenerator class as the token generator class. If the client-side bindings for the Web service uses IDAssertion...

  1. Set a token generator for the authentication token of the original client.

  2. Define the com.ibm.wsspi.wssecurity.token.IDAssertion.isUsed property and set its value to true in the Token Generator Dialog window within an assembly tool. If the original client is using a username token for authentication and if the target Web service is using BasicAuth for authentication, configure the following token generators in the client-side binding file:

     • The username token of the original client. Set the com.ibm.wsspi.wssecurity.token.IDAssertion.isUsed property in the token generator of the original client.

     • The username token of the intermediary Web service.

• Migrate the Security Response Receiver Binding Configuration section from a Java EE V1.3 application to a Java EE Version 1.4 application. Migrating the Security Response Receiver Binding Configuration section is similar to migrating the Request Receiver Binding Configuration Details section of the server-side bindings configuration. Migrate this information under the Security Response Consumer Binding Configuration section.

  See Migrate the server-side bindings file.

  To configure a nonce in the binding file, define the com.ibm.wsspi.wssecurity.token.username.addNonce property in the token generator of the username token.

 

Results

This set of steps describe the types of information that we need to migrate the WS-Security client-side bindings configuration for a Java EE Version 1.3 application to a Java EE V1.4 application.

 

Next steps

Verify that we have migrated both the server-side and the client-side extension and binding configurations for a Java EE V1.3 application to a Java EE Version 1.3 application.

See Migrate JAX-RPC WS-Security applications to V7.0 applications.

 

Related tasks

Migrate the JAX-RPC server-side extensions configuration
Migrate the client-side extensions configuration
Migrate the server-side bindings file
Migrate JAX-RPC WS-Security applications to V7.0 applications