Why and when to perform this task
This article provides general information about migrating the Web services security client-side extensions configuration for a Java 2 Platform, Enterprise Edition (J2EE) Version 1.3 application to a J2EE Version 1.4 application. The steps are based on typical scenarios, but the steps are not all-inclusive.J2EE Version 1.3 security extensions for Web services security | J2EE Version 1.4 extensions for Web services security |
---|---|
Request Sender Configuration | Request Generator Configuration |
Response Receiver Configuration | Response Consumer Configuration |
Consider the following steps to migrate the client-side extensions configuration from a J2EE Version 1.3 application to a J2EE Version 1.4 application. These steps are dependent upon your specific configuration.
Steps for this task (dependent on configuration)
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.
Result
This set of steps describe the types of information that you need to migrate the client-side extensions configuration for Web services security for a J2EE Version 1.3 application to a J2EE Version 1.4 application.What to do next
Migrate the server-side bindings configuration for a J2EE Version 1.3 application to a J2EE Version 1.4 application. For more information, see Migrating the server-side bindings file.Related tasks
Migrating the server-side extensions configuration
Migrating the server-side bindings file
Migrating the client-side bindings file
Migrating Version 5.x applications with Web services security to Version
6 applications