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 configurations

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

[Version 6.0.2] Use this option to work with WS-Security configurations 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 configurations 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 configurations to secure the SOAP messages that pass between service requesters (clients) and inbound services, and between outbound services and target Web services. Configurations specify the level of security that you require (for example "The body must be signed"). This level of security is then implemented through the run-time information contained in a WS-Security binding.

You receive the security configuration information direct from the service requester or target service provider, in the form of an ibm-webservicesclient-ext.xmi file for the client, and an ibm-webservices-ext.xmi file for the target Web service, which contain the information on the levels of security (integrity, confidentiality and identification) that are required. You extract the information from these .xmi files, then manually enter it into the WS-Security configuration forms.

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

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 bindings
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_conf.html

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