Thanks for the quick fix. I have a couple questions: - When do you think WSS4J 1.6.4 may be released? - Can I just upgrade WSS4J to 1.6.4 to fix this problem? Or do I need to upgrade CXF to 2.5.1 as well?
-- View this message in context: http://cxf.547215.n5.nabble.com/Re-General-security-error-Provided-SAML-token-does-not-contain-a-suitable-key-tp4990489p4998600.html Sent from the cxf-dev mailing list archive at Nabble.com.
