Re: WSSecurityEngine: Callback supplied no password for: null when using useReqSigCert for encryptionUser in multiple client scenario.

lace where the OUT interceptor can grab it. > > Dan > > > On Wed April 1 2009 9:31:52 am santhosh00724 wrote: >> I was debugging the code with WSS4J 1.5.6 version. When the control goes >> into the WSHandler's function >> >> priva

WSSecurityEngine: Callback supplied no password for: null when using useReqSigCert for encryptionUser in multiple client scenario.

I am getting following error while running a service with multiple clients with "Timestamp Signature Encrypt " action for the interceptor & It works fine for single client scenario. but not for multiple clients. I looked into many mailing lists but couldn't find any information. It is a two way e

RE: WSSecurityEngine: Callback supplied no password for: null when using useReqSigCert for encryptionUser in multiple client scenario.

My Client Config : http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp;{Element}{htt

RE: WSSecurityEngine: Callback supplied no password for: null when using useReqSigCert for encryptionUser in multiple client scenario.

Thank you for reply, This is what I am getting now. I am using CXF 2.1.3. is this a problem. I tried using CXF 2.2 & 2.1.4 I am getting : java.lang.ClassNotFoundException: org.springframework.context.support.AbstractRefres hableConfigApplicationContext Santhosh. Original Exception with CXF 2.1.

RE: WSSecurityEngine: Callback supplied no password for: null when using useReqSigCert for encryptionUser in multiple client scenario.

hould contain and why is it returning null. I am trying to fix it if there is no patch for cxf to handle multiple clients .. please help.. Santhosh. santhosh00724 wrote: > > Thank you for reply, > > This is what I am getting now. I am using CXF 2.1.3. is this a problem. I >