Request generator (sender) binding configuration settings

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

1. Click Applications > Application Types > WebSphere enterprise applications > application_name .

2. Under Modules, click Manage modules.

3. Click the Uniform Resource Identifier (URI).

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

5. Under Request generator (sender) binding, click Edit custom.

Depending on the 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.

(zos) An assembly tool is not available on the z/OS platform.

If the security constraints are defined in the application, you must 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 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.

information for digital signature security constraints. The

Information type	Required or optional
Signing information	Required
Key information	Required
Key locators	Optional
Collection certificate store	Optional
Token generator	Optional
Properties	Optional

We can use the key locators and the collection certificate store defined at either the cell or the server-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 for encryption constraints. The binding information

Information type	Required or optional
Encryption information	Required
Key information	Required
Key locators	Optional
Collection certificate store	Optional
Token generator	Optional
Properties	Optional

We can use the key locators and the collection certificate store defined at either the cell or the server-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.

constraints. The binding information is used for signing

Information type	Required or optional
Token generator	Required
Collection certificate store	Optional
Properties	Optional

We can use the collection certificate store defined at either the cell-level or the server-level.

Use defaults

Select this option to use the default binding information from either the cell or the server-level.

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

Component

Enterprise bean in an assembled EJB module.

Port

Port in the web service defined during application assembly.

Web service

Name of the web service defined during application assembly.

Related tasks

Configure token generators using JAX-RPC to protect message authenticity at the application level

Request consumer (receiver) binding configuration settings

Response generator (sender) binding configuration settings

Response consumer (receiver) binding configuration settings