Request consumer (receiver) binding configuration settings

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

1. Click Applications > Enterprise applications > application.

2. Click Manage modules.

3. Click the URI.

4. Under Web Services Security Properties, click Web services: Server security bindings.

5. Under Request consumer (receiver) binding, click Edit custom.

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

If the security constraints are defined in the application, either define the corresponding binding information or select the Use defaults option on this panel and use the default binding information for the cell or server level. The default binding that is provided by WAS 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.

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

You can use the key locators, collection certificate stores, and trust anchors that are defined at either the server level or the cell level.

 

Encryption constraint (confidentiality)

The following table shows the required and optional binding information when the encryption constraint (confidentiality) is defined in the deployment descriptor.

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

You can use the key locators, collection certificate store, and trust anchors that are defined at either the server level or the cell level.

 

Security token constraint

The following table shows the required and optional binding information when the security token constraint is defined in the deployment descriptor.

Information type	Required or optional
Token consumer	Required
Collection certificate store	Optional
Trust anchors	Optional
Properties	Optional

You can use the collection certificate store and trust anchors that are defined at the server level or the cell level.

Use defaults

Select this option if you want to use the default binding information from the server or cell level.

If you select this option, the appserver checks for binding information on the server level. If the binding information does not exist on the server level, the appserver checks the cell level.

Port

Port in the Web service that is defined during application assembly.

Web service

Name of the Web service that is defined during application assembly.

---

 

Related tasks

Configure 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