Dalys, maybe the client is not configured to support signatureConfirmation. It's "on" per default, but it could be switched off using a WSDD setting. Can you check (or mail) the client's WSDD file?
Regards, Werner Dalys Sebastian wrote: > I am running Axis2 (version 0.93) with WSS4J enabled. The service is running > under > Tomcat5. I have JKS keystores setup for both client and server. > I am able to send a secure message from the client to the server and the > server responds > with a return message. But when the client reads the response, it's giving > the following > exception: > > WSHandler: Check Signature confirmation: got a SC element, but no stored SV; > nested > exception is: > org.apache.ws.security.WSSecurityException: WSHandler: Check Signature > confirmation: got a SC element, but no stored SV > > I fired up tcpmon and monitored the messages. I can find that in the message > that is send > from the client to server, there is a signature value element. > And in the response, I can find a signature confirmation with one of its > attributes as > the same value that the server send as 'signatureValue'. > Then, why does the client respond with this exception? > > Please help me to solve this problem. > Thanks, > Dalys > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
