Hi Yuriy, The log you attached only shows messages up to level INFO. Could you attach a log with message up to level FINE (or DEBUG)? WSS4J uses commons logging, so you'll need to add either log4j or the slf4j bridge for commons logging.
It sounds like it might be a bug in WSS4J with not finding the correct key to use to verify the signature. I'll need the more fine grained logs to check for sure. Alternatively, you could attach a sample project that reproduces the problem. Colm. On Tue, May 22, 2012 at 5:24 PM, Yuriy Flyud <[email protected]> wrote: > Thank you for response, Colm! > > Here is the full log attached: > http://cxf.547215.n5.nabble.com/file/n5708299/log.log log.log > > About the keystore on the client side - I use Kerberos/SPNego mechanism to > connect > to service with the help of my custom SpnegoClientAction implementation. > Does it care about this? > > I can attach my project if needed. > > Best regards, Yuriy. > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Error-message-from-server-cannot-be-decrypted-tp5708282p5708299.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
