Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - Security (WS-Security) > Configure Web Services Security during application assembly > Configure XML digital signature for v5.x web services with an assembly tool


Configure the client security bindings using an assembly tool

Use the web services client editor within an assembly tool to include the binding information, that describes how to run the security specifications found in the extensions, in the client EAR file.

There is an important distinction between v5.x and v6 and later applications. The information in this article supports v5.x applications only that are used with WAS Version 6.0.x and later. The information does not apply to Version 6.0.x and later applications.

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 an assembly tool to include the binding information in the client EAR file.

We 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 an assembly tool:


Procedure

  1. Import the web services client EAR file into an assembly tool. When you edit the client bindings on a server acting as a client, the same basic steps apply. See the related information on Assembly Tools.
  2. Switch to the Java EE perspective. Click Window > Open Perspective > J2EE.

  3. Click Application Client Projects > application_name > appClientModule > META-INF.
  4. Right-click the application-client.xml file, select Open with > Deployment descriptor editor. The Client Deployment Descriptor is displayed.

  5. Click the WS Extension tab and select the port QName bindings to configure. The Web Services Security extensions are configured for outbound requests and inbound responses. You need to configure the following information for Web Services Security extensions. These topics are discussed in more detail in other sections of the documentation.

    Request sender configuration details

    Details

    Configure the client for request signing: digitally signing message parts

    Integrity

    Configure the client for request signing: digitally signing message parts

    Confidentiality

    Configure the client for request encryption: Encrypting the message parts

    Login Config

    BasicAuth

    Configure the client for basic authentication: specifying the method

    IDAssertion

    Configure the client for identity assertion: specifying the method

    Signature

    Configure the client for signature authentication: specifying the method

    LTPA

    Configure the client for LTPA token authentication: specifying LTPA token authentication

    ID assertion

    Configure the client for identity assertion: specifying the method

    Add created time stamp

    Configure the client for request signing: digitally signing message parts

    Response receiver configuration details

    Required integrity

    Configure the client for response digital signature verification: verifying the message parts

    Required confidentiality

    Configure the client for response decryption: decrypting the message parts

    Add received time stamp

    Configure the client for response digital signature verification: verifying the message parts

  6. Click the WS binding tab and select the port qualified name binding to configure. The Web Services Security bindings are configured for outbound requests and inbound responses. You need to configure the following information for Web Services Security bindings. These topics are discussed in more details in other sections of the documentation.

    Security request sender binding configuration

    Signing information

    Configure the client for request signing: choosing the digital signature method

    Encryption information

    Configure the client for request encryption: choosing the encryption method

    Key locators

    Configure key locators using an assembly tool

    Login binding

    BasicAuth

    Configure the client for basic authentication: collecting the authentication information

    ID assertion

    Configure the client for identity assertion: collecting the authentication method

    Signature

    Configure the client for signature authentication: collecting the authentication information

    LTPA

    Configure the client for LTPA token authentication: collecting the authentication method information

    Security response receiver binding configuration

    Signing information 

    Configure the client for response digital signature verification: choosing the verification method

    Encryption information

    Configure the client for response decryption: choosing a decryption method

    Trust anchor

    Configure trust anchors using an assembly tool

    Certificate store list

    Configure the client-side collection certificate store using an assembly tool

    Key locators

    Configure key locators using an assembly tool


What to do next

When configuring the security request sender binding configuration, 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, 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.

Related configurations. The configurations must be synchronized with each other.

Client configuration Server configuration
Request sender Request receiver
Response receiver Response sender

Request sender
Request receiver
Response sender
Response receiver
Assembly tools
Configure the security bindings on a server acting as a client
Configure the server security bindings using an assembly tool
Configure the server security bindings
Secure web services for v5.x applications using XML digital signature

+

Search Tips   |   Advanced Search