Request consumer (receiver) binding configuration settings

Use this page to specify the binding configuration for the request consumer.

To view this administrative console page, complete the following steps:
  1. Click Applications > Application Types > WebSphere enterprise applications application_name.
  2. Click Manage modules.
  3. Click the Uniform Resource Identifier (URI).
  4. Under Web Services Security Properties, click Web services: Server security bindings.
  5. Under Request consumer (receiver) binding, click Edit custom.

Depending on your assigned security role when security is enabled, you might not have access to text entry fields or buttons to create or edit configuration data. Review the administrative roles documentation to learn more about the valid roles for the application server.

The security constraints or bindings are defined using the application assembly process before the application is installed.

[z/OS] An assembly tool is not available on the z/OS® platform.

The default binding that is provided by this product is a sample. Do not use this sample in a production environment without modifying the configuration. The security constraints define what is signed or encrypted in the Web services security message. The bindings define how to enforce the requirements.

Digital signature security constraint (integrity)

The following table shows the required and optional binding information when the digital signature security constraint (integrity) is defined in the deployment descriptor.
Table 1. Binding information for digital signature security constraints. The binding information is used for signing or encrypting messages.
Information type Required or optional
Signing information Required
Key information Required
Token consumer Required
Key locators Optional
Collection certificate store Optional
Trust anchors Optional
Properties Optional

Encryption constraint (confidentiality)

The following table shows the required and optional binding information when the encryption constraint (confidentiality) is defined in the deployment descriptor.
Table 2. Binding information for encryption constraints. The binding information is used for signing or encrypting messages.
Information type Required or optional
Encryption information Required
Key information Required
Token consumer Required
Key locators Optional
Collection certificate store Optional
Trust anchors Optional
Properties Optional

Security token constraint

The following table shows the required and optional binding information when the security token constraint is defined in the deployment descriptor.
Table 3. Binding information for security token constraints. The binding information is used for signing or encrypting messages.
Information type Required or optional
Token consumer Required
Collection certificate store Optional
Trust anchors Optional
Properties Optional

Use defaults

[Version 6 only]

Port

[Version 6 only]

Specifies the port in the Web service that is defined during application assembly.

Web service

[Version 6 only]

Specifies the name of the Web service that is defined during application assembly.




Related tasks
Configuring token consumers using JAX-RPC to protect message authenticity at the application level
Related reference
Request generator (sender) binding configuration settings
Response generator (sender) binding configuration settings
Response consumer (receiver) binding configuration settings
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:37:48 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=uwbs_reqcons
File name: uwbs_reqcons.html