i've made sure that i follow all steps as-is, yet the problem persists. what does a signed assertion look like..as the server expects it be? what insight may i derive on reasons of this error..why would CXF not sign the message as the policy expects it to? is this a defect?
-- View this message in context: http://cxf.547215.n5.nabble.com/Signing-SAML-assertions-for-OWSM-policies-tp5632914p5635486.html Sent from the cxf-dev mailing list archive at Nabble.com.
