Add or modify the configuration details for a WS-Security binding
that is configured for use with service integration bus-deployed Web services.
You use WS-Security bindings to secure the SOAP messages that pass between
service requesters (clients) and inbound services, and between outbound services
and target Web services.
Why and when to perform this task
WS-Security bindings provide the information that the run-time
environment needs to implement the WS-Security configuration (for example "To
sign the body, use this key"). You receive this security binding information
direct from the service requester or target service provider, in the form
of an ibm-webservicesclient-bnd.xmi file for the client,
and an ibm-webservices-bnd.xmi file for the target Web service.
You extract the information from these .xmi files, then manually
enter it into the WS-Security bindings forms.
Bindings are administered
independently from any Web service that uses them, so you can create a binding
then apply it to many Web services.
To list the WS-Security bindings,
and to view and modify their configuration details, complete the following
steps:
Steps for this task
- Start the administrative console.
- In the navigation pane, click . A list of WS-Security bindings is displayed in a WS-Security
bindings collection form.
Each available binding is flagged as one
of the following binding types:
- request consumer, for use when consuming requests from a client to an inbound service.
- request generator, for use when generating requests from an outbound service to a target Web service.
- response consumer, for use when consuming responses from a target Web service to an outbound service.
- response generator, for use when generating responses from an inbound service to a client.
![[Version 6.0.2]](../was602.gif)
For WS-Security Version 1.0:
- request consumer, for use when consuming requests from a client to an inbound service.
- request generator, for use when generating requests from an outbound service to a target Web service.
- response consumer, for use when consuming responses from a target Web service to an outbound service.
- response generator, for use when generating responses from an inbound service to a client.
For WS-Security Draft 13:
- request receiver, for use when receiving requests from a client to an inbound service.
- request sender, for use when sending requests from an outbound service to a target Web service.
- response receiver, for use when receiving responses from a target Web service to an outbound service.
- response sender, for use when sending responses from an inbound service to a client.
![[Version 6.0.2]](../was602.gif)
Each available binding is also
flagged as complying with either the
Web Services Security (WS-Security) 1.0
specification or the WS-Security Draft 13 specification.
Deprecation note: The WS-Security Draft 13 specification is deprecated in WebSphere
Application Server Version 6, and you should only use it to enable inter-operation
between applications running in WebSphere Application Server Version 5 and
Version 6, or to allow continued use of an existing Web services client application
that has been written to the WS-Security Draft 13 specification.
- Click the name of a WS-Security binding in the list. The
current settings for this WS-Security binding are displayed.
- Modify the configuration details for this WS-Security binding. For detailed reference information about each value that you can set,
click on the associated link in the following tables:
- Save your changes to the master configuration.
If the processing completes successfully, the list of WS-Security
bindings is redisplayed. Otherwise, an error message is displayed.