Migrate the client-side bindings file
You can migrate the Web services security client-side binding configuration for a Java 2 Platform, Enterprise Edition V1.3 application to a J2EE V1.4 application.
Overview
The following table lists the mapping of the top-level sections under the client-side Port Bindings tab within a J2EE V1.3 application to a J2EE V1.4 application.
Table 1. The mapping of the configuration sections J2EE V1.3 binding configuration for Web services security J2EE V1.4 binding configuration for Web services 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 J2EE V1.3 application to a J2EE V1.4 application. These steps are dependent upon your specific configuration. The steps are based on typical scenarios, but the steps are not all-inclusive.
Procedure
- Migrate the information in the Security Request Sender Binding Configuration section in a J2EE V1.3 application to a J2EE 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. For more information, see Migrating the server-side bindings file.
- Migrate the information in the Key Locators, Signing Information, and the Encryption Information sections of the J2EE V1.3 application to a J2EE V1.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 Migrating the server-side bindings file.
- Migrate the information in the Login Bindings section in a J2EE V1.3 application to a J2EE 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...
- Configure a token generator for the authentication token of the original client.
- 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 J2EE V1.3 application to a J2EE V1.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. For more information, see Migrating 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 Web services security client-side bindings configuration for a J2EE V1.3 application to a J2EE V1.4 application.
What to do next
Verify that you have migrated both the server-side and the client-side extension and binding configurations for a J2EE V1.3 application to a J2EE V1.3 application. For more information, see Migrating V5.x applications with Web services security to V6.1 applications.
Related tasks
Migrating the server-side extensions configuration
Migrating the client-side extensions configuration
Migrating the server-side bindings file
Migrating V5.x applications with Web services security to V6.1 applications