Configuring secure transmission of SOAP messages by using WS-Security
Configure service integration technologies for secure transmission of SOAP messages by using tokens, keys, signatures and encryption in accordance with the Web Services Security (WS-Security) specification.
Before you begin
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.
您只能搭配符合 Web Services for Java™ Platform、Enterprise Edition (Java EE) 或 Java Specification Requirements (JSR) 109 規格的 Web 服務應用程式,來使用 WS-Security。 如需相關資訊,請參閱Web Services Security and Java Platform, Enterprise Edition security relationship。如需如何使 Web 服務應用程式符合 JSR-109 標準的相關資訊,請參閱實作 JAX-RPC Web 服務用戶端或Implementing static JAX-WS web services clients。
About this task
- WS-Security bindings.
- WS-Security configurations.
The configurations resource type specifies the level of security that you require (for example "The body must be signed"), and the bindings resource type provides the information that the run-time environment needs to implement the configuration (for example "To sign the body, use this key"),
When you associate a WS-Security resource with a port, you choose from a list of WS-Security resources that you have previously configured as described in the following topics:
Procedure
What to do next
For an overview of how WS-Security is applied to service integration bus-deployed web services, see Service integration technologies and WS-Security. For detailed information about how WS-Security is implemented in WebSphere Application Server, see Web 服務訊息層次安全的標準和程式設計模型概觀. For more information about the WS-Security standard, see the Web Services Security (WS-Security) 1.0 specification.