Encrypting message elements in consumer security constraints with keywords

Complete the following steps to specify which message parts to check for encryption 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, you must configure either the client-side bindings in step 2 or the server-side bindings in step 3.

Click Window > Open Perspective > J2EE.
Optional: Locate the client-side bindings using the Project Explorer window. The Client Deployment Descriptor window is displayed. This Web service contains the extensions that you need to configure. Complete the following steps to locate the client-side bindings:
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.
Optional: Locate the server-side bindings using the Project Explorer window. The Web Services Editor window is displayed. This Web service contains the bindings that you need to configure. Complete the following steps to locate the server-side bindings:
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.
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.
Click Add to specify which parts of the message to check for encryption. 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.
Click Add under Message parts and select the message parts dialect. The http://www.ibm.com/websphere/webservices/wssecurity/dialect-was dialect specifies which message part to be checked for encryption using keywords. If you select this dialect, you can select one of the following keywords under Message parts keyword:
bodycontent

Specifies the user data portion of the message. If you select this keyword, the body is checked for encryption.

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 is checked for encryption.

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. You can encrypt the digestvalue element to secure the digest value. If you select this keyword, the digestvalue is checked for encryption.

Note: You must have a matching configuration for the generator.
In addition to the message parts, you also can specify that WebSphere^® Application Server check the encryption of the nonce and timestamp elements. For more information, see the following articles:
Click OK to save your configuration.

After you specify which message parts to check for encryption, you must specify which method is used to verify the encryption of the message parts. For more information, see Configuring encryption information for the consumer binding.