要求產生者連結 [設定]
如果要在主控台中檢視這個頁面,請按下列路徑:
.
You 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 generator with an outbound configuration. A request generator binding generates the requests from an outbound service to a target web service.
「配置」標籤
「配置」標籤顯示這個物件的配置內容。 這些內容會保留下來,即使停止並重新啟動執行時期環境也一樣。請參閱資訊中心作業說明,以取得如何將配置變更套用於執行時期環境的相關資訊。
一般內容
WS-Security 版本
Information | Value |
---|---|
必要 | 否 |
資料類型 | 字串 |
連結類型
Information | Value |
---|---|
必要 | 否 |
資料類型 | 字串 |
名稱
- 不可以 "."(句點)開頭。
- 不可以空格開頭或結尾。
- 它不能包含下列中的任何字元:\ / , # $ @ : ; " * ? < > | = + & % '
Information | Value |
---|---|
必要 | 是 |
資料類型 | 字串 |
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 that is defined here.
Information | Value |
---|---|
必要 | 否 |
資料類型 | 布林 |
Web Services Security namespace
Specifies the namespace that is 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 |
---|---|
必要 | 是 |
資料類型 | 下拉清單 |
其他內容
- Signing information
- Specifies the 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
- Specifies the 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
- Specifies the parameters for the token generator. The information is used only on the generator side to generate the security token. Because you can plug in a custom token generator, you must specify a Java™ class name.
- Key information
- Specifies the 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. You 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.
- Properties
- Specifies additional properties for the configuration.