Adding a nonce for confidentiality in consumer security constraints with keywords

 

Before you begin

Prior to completing this task, import your application into an assembly tool. For information on how to import your application, see Import enterprise applications.

 

Overview

Nonce for confidentiality is used to specify that the nonce is embedded in a particular element within the message and that the element is encrypted. Complete the following steps to check the confidentiality of an element that has nonce embedded in it and is encrypted using keywords when you configure the consumer security constraints for either the response consumer or the request consumer. The response consumer is configured for the client and the request consumer is configured for the server. In the following steps, configure either the client-side extensions in step 2 or the server-side extensions in step 3.

 

Procedure

  1. Start the assembly tool and click Window > Open Perspective > J2EE.

  2. Optional: Locate the client-side extensions using the Project Explorer window. The Client Deployment Descriptor window is displayed. This Web service contains the extensions that we need to configure. Complete the following steps to locate the client-side extensions:

    1. Expand the Web Services > Client section and double-click the name of the Web service.

    2. Click the WS Extension tab and expand the Response Consumer Configuration section.

  3. Optional: Locate the server-side extensions using the Project Explorer window. The Web Services Editor window is displayed. This Web service contains the extensions that we need to configure. Complete the following steps to locate the server-side extensions:

    1. Expand the Web Services > Services section and double-click the name of the Web service.

    2. Click the Extensions tab and expand the Request Consumer Service Configuration Details section.

  4. Expand the Required Confidentiality section. Confidentiality refers to encryption while integrity refers to digital signing. Confidentiality reduces the risk of someone intercepting the message as it moves across a network. With confidentiality specifications, the message is encrypted before it is sent and decrypted when it is received at the intended target. For more information on encryption, see XML encryption.

  5. Click Add to specify that the element within which a nonce is added and encrypted, is checked for confidentiality. The Required Confidentiality Dialog window is displayed. Complete the following steps to specify a configuration:

    1. Specify a name for the confidentiality element in the Required Confidentiality Name field.

    2. Specify a usage type in the Usage type field. This field specifies the requirement for the confidentiality element. The value of this attribute is either Required or Optional.

  6. Under Nonce, click Add and select the Nonce dialect. The http://www.ibm.com/websphere/webservices/wssecurity/dialect-was dialect specifies the message part which has an embedded nonce is verified for encryption. If you select this dialect, one can select one of the following keywords under Nonce keyword:

    bodycontent

    Specifies the user data portion of the message. If this keyword is selected, the nonce is embedded in the SOAP message body and the body along with the embedded nonce is checked for confidentiality.

    usernametoken

    Specifies a username token that contains the basic authentication information such as a user name and a password. Usually, the username token is encrypted so that the user information is secure. If you select this keyword, the username token element along with the embedded nonce is checked for confidentiality.

    digestvalue

    Specifies a unique digest value. When a part of the Simple Object Access Protocol (SOAP) message is signed, a unique digest value is created and is used by the receiving party to check the integrity of the message. We can encrypt the digestvalue element to secure the digest value. If you select this keyword, the digestvalue element along with the embedded nonce is checked for confidentiality.

  7. If you have not specified message parts in Required Confidentiality, in the Message Parts section, click Add to add message parts. You must define at least one message part in Required Confidentiality for specifying Nonce in Required Confidentiality.

  8. In the Message Parts section, select the message parts keyword.

  9. Click OK to save the configuration changes.

    Note: These configurations for the consumer and the generator must match.

    In addition to the nonce, one can specify that the timestamp element is checked for confidentiality. For more information, see the following articles:

 

What to do next

After you specify which message parts to check for confidentiality, specify which method is used to verify the encryption. For more information, see Configuring encryption information for the consumer binding with an assembly tool.


 

See Also


XML digital signature

 

Related Tasks


Adding a stand-alone time stamp in consumer security constraints
Adding time stamps for confidentiality in consumer security constraints with keywords
Adding time stamps for confidentiality in consumer security constraints with an XPath expression
Configuring encryption information for the consumer binding with an assembly tool