WS-Security bindings for consumption and generation of requests and responses.
To view this pane in the console, click the following path:
.
To browse or change the properties of a listed item, select its name in the list.
To act on one or more of the listed items, select the check boxes next to the names of the items that you want to act on, then use the buttons provided.
To change which entries are listed, or to change the level of detail that is displayed for those entries, use the Filter settings.
You can configure the service integration bus for secure transmission of SOAP messages using tokens, keys, signatures and encryption in accordance with the Web Services Security (WS-Security) 1.0 specification.
Alternatively, you can configure the bus in accordance with the previous WS-Security specification, WS-Security Draft 13 (also known as the Web Services Security Core Specification). However, use of WS-Security Draft 13 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.
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. 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"),
Bindings are administered independently from any Web service that uses them, so you can create a binding then apply it to many Web services. However, the security requirements for an inbound service (which acts as a target Web service) are significantly different to those required for an outbound service (which acts as a client). Consequently, bindings are further divided into sub-types: