2012/4/4 Philippe A. <futhar...@gmail.com> > > <ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy";> > <ramp:user>...</ramp:user> > > <ramp:passwordCallbackClass>client.PWCBHandler</ramp:passwordCallbackClass> > <ramp:userCertAlias>...</ramp:userCertAlias> > <ramp:encryptionUser>...</ramp:encryptionUser> > <ramp:encryptionCrypto> > <ramp:crypto > provider="org.apache.ws.security.components.crypto.Merlin"> > <ramp:property > name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property> > <ramp:property > name="org.apache.ws.security.crypto.merlin.file">keystore</ramp:property> > <ramp:property > name="org.apache.ws.security.crypto.merlin.keystore.password">...</ramp:property> > </ramp:crypto> > </ramp:encryptionCrypto> > <ramp:signatureCrypto> > <ramp:crypto > provider="org.apache.ws.security.components.crypto.Merlin"> > <ramp:property > name="org.apache.ws.security.crypto.merlin.keystore.type">JKS</ramp:property> > <ramp:property > name="org.apache.ws.security.crypto.merlin.file">keystore</ramp:property> > <ramp:property > name="org.apache.ws.security.crypto.merlin.keystore.password">...</ramp:property> > </ramp:crypto> > </ramp:signatureCrypto> > </ramp:RampartConfig> >
On a slightly different topic, I just found out that specifying signatureCrypto is not required when setting up a symmetric binding. Axis will reuse encryptionCrypto properties for signature. -- Philippe
