Configuring a policy set and bindings for XML Digital Signature with client and provider application specific bindings
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.
Before you begin
This task assumes that the service provider and client that you are configuring are in the
JaxWSServicesSamples
application. For more information about obtaining this
application, see Obtaining the JAX-WS Web Services samples.
*=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:
About this task
Configure WS-Security policy set to use only the XML-Digital Signature WS-Security constraint and 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 traditional 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)