You can 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.
Before you begin
Prior to completing this task, you must import your application into
an assembly tool.
For information on how to import
your application, see Importing
enterprise applications.
About this task
Complete the following steps. You must configure either the client-side
bindings in step 2 or the server-side bindings in step 3.
Procedure
- Start the assembly tool and 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 must configure.
Complete the following steps to locate the client-side bindings:
- Expand the Web Services > Client section and double-click the
name of the Web service.
- 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 must configure. Complete the
following steps to locate the server-side bindings:
- Expand the Web Services > Services section and double-click
the name of the Web service.
- Click the Extensions tab and expand the Request Consumer
Service Configuration Details section.
- Expand the Required Confidentiality section. Confidentiality
refers to encryption and 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:
- Specify a name for the confidentiality element in the Required
Confidentiality Name field.
- 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.