+

Search Tips   |   Advanced Search

Response receiver [Settings]

Draft 13 WS-Security binding for consumption of responses from a target.

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

Service integration -> Web services -> WS-Security bindings -> response-receiver-binding_name.

This panel is one of a set of panels that allow us to configure the service integration bus in accordance with WS-Security Draft 13 (also known as the 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.


Configuration tab

The Configuration tab shows configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted.


General Properties


WS-Security version

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

Information Value
Required No
Data type String


Binding Type

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

Information Value
Required No
Data type String


Name

The name of the binding.

Information Value
Required Yes
Data type String


Additional Properties

Signing information

Configuration for the signing parameters. We also can use these parameters for X.509 certificate validation when the authentication method is IDAssertion and the ID type is X509Certificate in the server-level configuration. In such cases, only fill in the Certificate path field.

Encryption information

Configuration for the XML encryption and decryption parameters. If the data and key encryption algorithms are specified, the application server only accepts elements that are encrypted with those algorithms.

Trust anchors

List of keystore configurations that contain root-trusted certificates. These configurations are used for certificate path validation of the incoming X.509-formatted security tokens. We must create the keystore using the key tool utility. Do not use the key management utility because it does not create a keystore with the expected format.

Collection certificate store

List of untrusted, intermediate certificate files. This collection certificate store is used for certificate path validation of incoming X.509-formatted security tokens. The root-trusted certificates are specified in the Trust anchors panel.

Key locators

List of key locator configurations that retrieve the key for signature and encryption. We can customize a key locator class to retrieve keys from other types of repositories. The default implementation retrieves keys from a keystore.