Request generator binding. settings
WS-Security binding for the generation of outbound request to a target.
Console path:
Service integration -> Web services -> WS-Security bindings -> request-generator-binding_name.
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.
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.
We use a request generator with an outbound configuration. A request generator binding generates the requests from an outbound service to a target web service.
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.
This name must be unique, and it must obey the following syntax rules:
- It must not start with "." (a period).
- It must not start or end with a space.
- It must not contain any of the following characters: \ /, # $ @ : ; " * ? < > | = + & % '
Information Value Required Yes Data type String
Use defaults
Specifies whether to use the default binding information. When this option is enabled, Web Services Security uses the default binding information instead of the custom binding information defined here.
Information Value Required No Data type Boolean
Web Services Security namespace
Namespace used by Web Services Security to send a request. However, this field configures only the name space value and does not enforce the semantics of the specification that is related to the namespace. Web Services Security uses the processing semantic only in draft 13 of the OASIS specification.
Information Value Required Yes Data type drop-down list
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.
- Token generators
- Parameters for the token generator. The information is used only on the generator side to generate the security token. Because we can plug in a custom token generator, specify a Java class name.
- Key information
- Related configuration needed to generate the key for XML digital signature or XML encryption.
- 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.
- 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.
- Properties
- Specifies additional properties for the configuration.