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

WS-Security configurations collection

WS-Security configurations for inbound and outbound services.

To view this administrative console page, click Service integration > Web services > WS-Security configurations.

To browse or change a listed item, select its name in the list.

To act on one or more of the listed items, select the check boxes next to the names of the items that you want to act on, then use the buttons provided.

To change what entries are listed, or to change what information is shown for entries in the list, use the Filter settings.

You can configure the service integration bus for secure transmission of SOAP messages using tokens, keys, signatures and encryption in accordance with the Web Services Security (WS-Security) 1.0 specification.

[Version 6.0.2] Alternatively, you 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). However, 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 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.

Configurations are administered independently from any Web service that uses them, so you can create a configuration then apply it to many Web services. However, the security requirements for an inbound service (which acts as a target Web service) are significantly different to those required for an outbound service (which acts as a client). Consequently, configurations are further divided by service type (inbound or outbound).

General properties

Name
The name of the WS-Security configuration.
Service type
The type of service the WS-Security configuration applies to.

Buttons

New Click this button to create a new instance of this object type.
Delete Click this button to delete a selected instance of this object type. You must first have selected the object to be deleted.

Reference topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\sibuswssecurity\SIBWSSecurityServiceConfigs_CollectionForm.html

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