Can you print the stacktrace you are getting? I think there is a bug in CXF in that it does not set the CallbackHandler instance up for Signature processing, as for most cases we don't need a password to verify signatures. However, for this case the CallbackHandler is expected to supply a key corresponding to the EncryptedKeySHA1 digest. Can you change the way the key is referenced on the server side, to issuer serial, or SKI Identifier or something which is clearer as to what key is required?
Colm. On Thu, Mar 3, 2011 at 8:28 AM, mmerayo <[email protected]> wrote: > To complete my info i can say: > > Im testing it all in a maven 2 project > It has a test with Junit 4.8.1 > It is enabled with SpringTest 3.0.2 > My java version is jdk 1.6.0.18 > I'm using the new CFX 2.3.3 > The WJSS4j version is 1.5.11 > > The action I configured was > > inProps.put(WSHandlerConstants.ACTION, WSHandlerConstants.SIGNATURE); > > If i put ENCRYPT action the WSS4J is asking to the password to the callback > class y supply, but i don't know what pasword i should put to decrypt de > keyinfo, i tried the keystore one, but that doesn't work. > > Thanks. > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/WSS4JInInterceptor-getCallback-null-tp3406991p3407640.html > Sent from the cxf-user mailing list archive at Nabble.com. >
