Yes, I've been trying with 2.2.2. No luck. This is actually a showstopper for us because at the very least we need to combine username token with timestamp in order to be backwards compatible with our customers. I guess we are stuck with CXF 1.x for now. :-(
-- View this message in context: http://www.nabble.com/USERNAME_TOKEN-%2B-SIGNATURE-gives-%22General-security-error-%28WSSecurityEngine%3A-No-password-callback-supplied%29%22-tp21814109p23967209.html Sent from the cxf-user mailing list archive at Nabble.com.
