WS-Security bindings [Collection]

WS-Security bindings for consumption and generation of requests and responses.

To view this page in the console, click the following path:

Service integration -> Web services -> WS-Security bindings.

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 to act on, then use the buttons provided.

To change which entries are listed, or to change the level of detail displayed for those entries, use the Filter settings.

We 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, we can configure the bus in accordance with the previous WS-Security specification, WS-Security Draft 13 (Web Services Security Core Specification). Use of the WS-Security Draft 13 specification is deprecated, and should only be used to allow continued use of an existing web services client application written to the WS-Security Draft 13 specification.

We 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 we 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:

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.

Name

The name of the WS-Security binding.

Binding Type

The type of binding. This is one of request consumer, request generator, response consumer and response generator.

Security version

Identifies the version of the WS-Security specification this configuration uses.

Buttons

Button	Description
New	Create a new administrative object of this type.
Delete	Delete the selected items.