Kumar, cheked the nested exception - it is thrown by the keystore handling objects (java.security.*). The description / doc says that the method (call via getPrivateKey() ) was not able to get the private key. It does give not any information if the alias or password was wrong (due to obvious security reasons).
We had a similar problem in the mailing list, and it was due to w wrong setting of the password in the password callback class - can you check you if use the correct one with the correct password and usernames (AFAIK the new names are alice and bob). Sometimes an old callback class is in the classpath somewhere (Going from DLL hell directly into the jar chaos (tm) :-) ) Regards, Werner > -----Ursprüngliche Nachricht----- > Von: Kumar [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 22. Juni 2005 14:04 > An: Dittmann, Werner > Cc: [email protected]; [email protected] > Betreff: Re: Signature creation failed exception with WSS4J and AXIS > > > Hi Werner, > > Thank you the prompt response. I am using the keystore file > interop2.jks from ***ws-fx_20050620105356\ws-fx\wss4j\interop*** > directory and the > ***ws-fx_20050620105356\ws-fx\wss4j\interop\keys\README.txt*** file > says the password for the alias is password and the private key > password is also password. These settings I have given in the > wsstest.properties. Even I am able to open the keystore file using > KeyStore Explorer Application and view the certificate. > > Please correct me if I am wrong anywhere. > > Thanks & Regards, > Kumar. > > On 6/22/05, Dittmann, Werner <[EMAIL PROTECTED]> wrote: > > Kumar, > > > > as the exception say: Cannot create Signature > > Reason in nested Exception: cannot recover key. > > > > This means that somehow your alias (username), password > > or alike does not match to retrieve the private key to > > create the Signature. Pls check if all you certificate > > store(s) (usually *.jks or *.pfx files) are accessible > > either via classpath or usual file path, also you may need > > to check if all your certificates, private key are stored > > with the corret username (alias) and matchinh passwords. > > > > Regards, > > Werner > > > > > -----Ursprüngliche Nachricht----- > > > Von: Kumar [mailto:[EMAIL PROTECTED] > > > Gesendet: Mittwoch, 22. Juni 2005 12:32 > > > An: [email protected]; [email protected] > > > Betreff: Signature creation failed exception with WSS4J and AXIS > > > > > > > > > Hi All, > > > > > > I want to try a simple handson on how to implement X509 > Certificate > > > Token Profile with WSS4J and AXIS. I just want to use a X509 > > > Certificate as token and no username/password token , no > encryption > > > but just signing and verifying the signature using wss4j and axis. > > > > > > I am following the code in the ***ws-fx\wss4j\interop*** > directory of > > > wss4j binary and found that Ping5 web service is suitable for my > > > purpose (not so confident whether Ping5 example is the > right one for > > > me). > > > > > > When I run my web service client program to connect to > the service I > > > am getting below exception. In my TCPMonitor I am not seeing any > > > request soap message either and can anyone please suggest > what am I > > > missing here. > > > > > > > > > Exception in thread "main" AxisFault > > > faultCode: > > > {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException > > > faultSubcode: > > > faultString: WSDoAllSender: Signature: error during message > > > procesingorg.apache.ws.security.WSSecurityException: Signature c > > > reation failed; nested exception is: > > > java.security.UnrecoverableKeyException: Cannot > recover key > > > faultActor: > > > faultNode: > > > faultDetail: > > > {http://xml.apache.org/axis/}stackTrace:WSDoAllSender: > > > Signature: error during message procesingorg.apache.ws.securit > > > y.WSSecurityException: Signature creation failed; nested > exception is: > > > java.security.UnrecoverableKeyException: Cannot > recover key > > > at > > > org.apache.ws.axis.security.WSDoAllSender.performSIGNAction(WS > > > DoAllSender.java:414) > > > at > > > org.apache.ws.axis.security.WSDoAllSender.invoke(WSDoAllSender > > > .java:320) > > > at > > > org.apache.axis.strategies.InvocationStrategy.visit(Invocation > > > Strategy.java:32) > > > at > > > org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) > > > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) > > > at > > > org.apache.axis.client.AxisClient.invoke(AxisClient.java:121) > > > at > org.apache.axis.client.Call.invokeEngine(Call.java:2754) > > > at org.apache.axis.client.Call.invoke(Call.java:2737) > > > at org.apache.axis.client.Call.invoke(Call.java:2413) > > > at org.apache.axis.client.Call.invoke(Call.java:2336) > > > at org.apache.axis.client.Call.invoke(Call.java:1793) > > > at ping.PingBindingStub.ping(PingBindingStub.java:154) > > > at ping.Client.main(Client.java:87) > > > > > > {http://xml.apache.org/axis/}hostname:hyddl0337 > > > > > > WSDoAllSender: Signature: error during message > > > procesingorg.apache.ws.security.WSSecurityException: Signature > > > creation failed > > > ; nested exception is: > > > java.security.UnrecoverableKeyException: Cannot > recover key > > > at > > > org.apache.ws.axis.security.WSDoAllSender.performSIGNAction(WS > > > DoAllSender.java:414) > > > at > > > org.apache.ws.axis.security.WSDoAllSender.invoke(WSDoAllSender > > > .java:320) > > > at > > > org.apache.axis.strategies.InvocationStrategy.visit(Invocation > > > Strategy.java:32) > > > at > > > org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) > > > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) > > > at > > > org.apache.axis.client.AxisClient.invoke(AxisClient.java:121) > > > at > org.apache.axis.client.Call.invokeEngine(Call.java:2754) > > > at org.apache.axis.client.Call.invoke(Call.java:2737) > > > at org.apache.axis.client.Call.invoke(Call.java:2413) > > > at org.apache.axis.client.Call.invoke(Call.java:2336) > > > at org.apache.axis.client.Call.invoke(Call.java:1793) > > > at ping.PingBindingStub.ping(PingBindingStub.java:154) > > > at ping.Client.main(Client.java:87) > > > > > > > > > > > > > > > Thanks & Regards, > > > Kumar > > > > > >
