Why and when to perform this task
When configuring a client for Web services security, the bindings describe how to run the security specifications found in the extensions. Use the Web services client editor within the Assembly Toolkit to include the binding information in the client enterprise archive (EAR) file.You can configure the client-side bindings from a pure client accessing a Web service or from a Web service accessing a downstream Web service. This document focuses on the pure client situation. However, the concepts, and in most cases the steps, also apply when a Web service is configured to communicate downstream to another Web service that has client bindings. Complete the following steps to edit the security bindings on a pure client (or server acting as a client) using the Assembly Toolkit:
Steps for this task
http://www.ibm.com/support/docview.wss?rs=180&context=SSEQTP &q=ASTK&uid=swg24005125&loc=en_US&cs=utf-8&lang=en+en
Request sender configuration details
Response receiver configuration details
Security request sender binding configuration
Security response receiver binding configuration
What to do next
Note: When configuring the security request sender binding configuration, you must synchronize the information used to perform the specified security with the security request receiver binding configuration, which is configured in the server EAR file. These two configurations must be synchronized in all respects because there is no negotiation during run time to determine the requirements of the server.
For example, when configuring the encryption information in the security request sender binding Configuration, you must use the public key from the server for encryption. Therefore, the key locator that you choose must contain the public key from the server configuration. The server must contain the private key to decrypt the message. This example illustrates the important relationship between the client and server configuration. Additionally, when configuring the security response receiver binding configuration, the server must send the response using security information known by this client security response receiver binding configuration.
The following table shows the related configurations
between the client and the server. The client request sender and the server
request receiver are relative configurations that must be synchronized with
each other. The server response sender and the client response receiver are
related configurations that must be synchronized with each other. Note that
the related configurations are end points for any request or response. One
end point must communicate its actions with the other end point because run
time requirements are not negotiated.
Client configuration | Server configuration |
---|---|
Request sender | Request receiver |
Response receiver | Response sender |