You can create a custom policy set and application specific bindings for using XML Digital Signature to sign the body of the request and response SOAP messages.
This task assumes that the service provider and client that you are configuring are in the JaxWSServicesSamples application. Refer to the topic Accessing Samples for more information on how to obtain and install this application.
*=info:com.ibm.wsspi.wssecurity.*=all:com.ibm.ws.webservices.wssecurity.*=all: com.ibm.ws.wssecurity.*=all: com.ibm.xml.soapsec.*=all: com.ibm.ws.webservices.trace.*=all: com.ibm.ws.websvcs.trace.*=all:com.ibm.ws.wssecurity.platform.audit.*=off:
This procedure explains the actions you need to complete to configure WS-Security policy set to use only the XML-Digital Signature WS-Security constraint. This procedure also explains the actions you need to complete to configure XML Digital Signature application specific custom bindings for a client and provider.
The keystores that are used in this procedure are provided with WebSphere Application Server and are installed in every profile that is created. You can use the ${USER_INSTALL_ROOT} variable directly in the configuration to conveniently point to the keystore locations without using a fully-qualified path. ${USER_INSTALL_ROOT} resolves to a path such as c:/WebSphere/AppServer/profiles/AppSrv01.
${USER_INSTALL_ROOT}/etc/ws-security/samples/dsig-sender.ks ${USER_INSTALL_ROOT}/etc/ws-security/samples/dsig-receiver.ks
* Services > Service Providers > (AppName) * Services > Service clients > (AppName)
The JaxWSServicesSamples web services application is configured to use XML Digital Signature to sign the body for both the SOAP request and response.
In this information ...Related concepts
Related tasks
| IBM Redbooks, demos, education, and more(Index) |