Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Request consumer binding [Settings]
WS-Security binding for the consumption of inbound requests from the caller.
Service integration -> Web services -> WS-Security bindings -> request-consumer-binding_name .
We can configure the service integration bus for secure transmission of SOAP messages by using tokens, keys, signatures and encryption in accordance with the Web Services Security (WS-Security) 1.0 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.
You use a request consumer with an inbound configuration. A request consumer binding consumes the requests from a client to an inbound service.
Configuration tab
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.
Required No Data type String
Binding Type
The type of binding. This is one of request consumer, request generator, response consumer and response generator.
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: \ / , # $ @ : ; " * ? < > | = + & % '
Required Yes Data type String
Use defaults
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 that is defined here.
Required No Data type Boolean
Additional Properties
Signing information
Configuration for the signing parameters. You 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 consumers
Parameters for the token consumer. The information is used only on the consumer side to process the security token. Because you can plug in a custom token consumer, specify a Java class name.
Key information
Related configuration that is needed to generate the key for XML digital signature or XML encryption.
Key locators
Specifies a 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
Specifies a 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.
Trust anchors
Specifies a 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. 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.
Properties
Specifies additional properties for the configuration.
Administrative console buttons
Administrative console preferences