WAS v8.5 > Secure applications > Secure web services > Secure bus-enabled web servicesConfigure secure transmission of SOAP messages using WS-Security
Configure service integration technologies for secure transmission of SOAP messages using tokens, keys, signatures and encryption in accordance with the Web Services Security (WS-Security) specification.
We can configure the service integration bus for secure transmission of SOAP messages using tokens, keys, signatures and encryption in accordance with the WS-Security 1.0 specification.
Alternatively, we can configure the bus in accordance with the previous WS-Security specification, WS-Security Draft 13 (also known as the Web Services Security Core Specification).
Use of WS-Security Draft 13 was deprecated in WebSphere Application Server v6.0. Use of WS-Security Draft 13 is deprecated, and you should only use it to allow continued use of an existing web services client application that has been written to the WS-Security Draft 13 specification.
We can only use WS-Security with web service applications that comply with the Web Services for Java EE or Java Specification Requirements (JSR) 109 specification. For more information, see Web Services Security and Java Platform, Enterprise Edition security relationship. For information about how to make the web service applications JSR-109 compliant, see Implement JAX-RPC web services clients or Implement static JAX-WS web services clients. To protect a service integration bus-deployed web service, we can apply the following types of WS-Security resource to the inbound or outbound ports the service uses:
- 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 the run-time environment needs to implement the configuration (for example "To sign the body, use this key"),
When associate a WS-Security resource with a port, you choose from a list of WS-Security resources that we have previously configured as described in the following topics:
We can associate any binding with any configuration, so ensure that you choose a valid combination.
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 WAS, see Programming models for web services message-level security. For more information about the WS-Security standard, see the WS-Security 1.0 specification.
Related concepts:
Service integration technologies and WS-Security
Web Services Security and Java Platform, Enterprise Edition security relationship
Related
Programming models for web services message-level security
Secure web services applications using the WSS APIs at the message level
Administer the bus-enabled web services resources
Implement static JAX-WS web services clients
Implement JAX-RPC web services clients