WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Working with service integration technologies WS-Security bindings

[Version 6.0.1 and earlier] Use this option to work with WS-Security bindings that comply with the Web Services Security (WS-Security) 1.0 specification.

[Version 6.0.2] Use this option to work with WS-Security bindings that comply with either the Web Services Security (WS-Security) 1.0 specification, or the previous WS-Security specification, WS-Security Draft 13 (also known as the Web Services Security Core Specification).
Deprecation note: Use of WS-Security Draft 13 is deprecated in WebSphere Application Server Version 6, and you should only use it to enable inter-operation between applications running in WebSphere Application Server Version 5 and Version 6, or to allow continued use of an existing Web services client application that has been written to the WS-Security Draft 13 specification.

You get, from the owning parties, the WS-Security bindings for the client (in the case of an inbound service) and the target Web service (in the case of an outbound service).

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. WS-Security 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"),

You receive this security binding information direct from the service requester or target service provider, in the form of an ibm-webservicesclient-bnd.xmi file for the client, and an ibm-webservices-bnd.xmi file for the target Web service. You extract the information from these .xmi files, then manually enter it into the WS-Security bindings forms.

WebSphere Application Server also includes a set of default WS-Security binding objects. However if you are using either of the single server products WebSphere Application Server or WebSphere Application Server Express, then these default bindings are configured within the application server (under the administrative console option Servers > Application servers server_name [Configuration tab, Security section] > Web services: Default bindings for Web services security) and are not available for use with service integration technologies-enabled Web services.

If you are administering a WebSphere Application Server Network Deployment installation, then the default WS-Security bindings are configured for the cell (under the administrative console option SecurityWeb services) and are available for use with service integration technologies-enabled Web services.

From the administrative console, you can complete the following service integration tasks for WS-Security bindings:

Related concepts
Service integration technologies and WS-Security
Related tasks
Getting WS-Security information from the owning parties
Working with service integration technologies WS-Security configurations
Securing Web services based on WS-Security 1.0
Securing Web services based on WS-Security Draft 13

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjw_wss_bind.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)