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

Modifying an existing WS-Security configuration

Use this task to add or modify the configuration details for a WS-Security configuration that is configured for use with service integration bus-deployed Web services.

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).

To list the WS-Security configurations, and to view and modify their configuration details, complete the following steps:

  1. Start the administrative console.
  2. In the navigation pane, click Service integration > Web services > WS-Security configurations. A list of WS-Security configurations is displayed in a WS-Security service configurations collection form.

    Each available configuration is flagged as either Inbound or Outbound. You use an inbound configuration to secure the SOAP messages that pass between a service requester (client) and an inbound service (which acts as a target Web service). You use an outbound configuration to secure the SOAP messages that pass between an outbound service (which acts as a client) and a target Web service.

    [Version 6.0.2] Each available configuration is also flagged as complying with either the Web Services Security (WS-Security) 1.0 specification or the WS-Security Draft 13 specification.
    Deprecation note: The WS-Security Draft 13 specification 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.
  3. Click the name of a WS-Security configuration in the list. The current settings for this WS-Security configuration are displayed.
  4. Modify the configuration details for this WS-Security configuration. For detailed reference information about each value that you can set, click on the associated link in the following table:
  5. Apply the changes.
If the processing completes successfully, the list of WS-Security configurations is redisplayed. Otherwise, an error message is displayed.
Related concepts
Service integration technologies and WS-Security

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_config.html

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