I see. I should then look into the certificate in my store. I noticed that client generated <ec:InclusiveNamespaces PrefixList="soap">, <..PrefixList=""> within my <ds:CanonicalizationMethod> and <ds:Transform> elements, respectively and SoapUI did not. I'm pretty sure this could relate to my Hash Mismatch error.
Is there way to not generate inclusivenamespaces within the policy? -- View this message in context: http://cxf.547215.n5.nabble.com/x-509-security-token-tp5150380p5505664.html Sent from the cxf-user mailing list archive at Nabble.com.
