Use this page to specify the binding configuration for the request
generator.
To view this WebSphere
® Application
Server administrative console page, complete the following steps:
- Click Applications > Enterprise applications > application_name.
- Under Related items, click EJB modules or Web modules.
- Click the Uniform Resource Identifier (URI).
- Under Additional properties, click Web services: Client security bindings.
- Under Request generator (sender) 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, 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 WebSphere Application Server 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 |
| Key locators |
Optional |
| Collection certificate store |
Optional |
| Token generator |
Optional |
| Properties |
Optional |
You can use the key locators and the collection certificate store
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 |
| Key locators |
Optional |
| Collection certificate store |
Optional |
| Token generator |
Optional |
| Properties |
Optional |
You can use the key locators and the collection certificate store
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 generator |
Required |
| Collection certificate store |
Optional |
| Properties |
Optional |
You can use the collection certificate store that is defined at either
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, WebSphere Application Server checks
for binding information on the server level
If you select this option, WebSphere 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.