The solution is to edit the WSDL and add in a <wsp:Policy/> child to the KeyValueToken policy. I've just merged a update to CXF 3.0.1-SNAPSHOT + 2.7.X-SNAPSHOT to relax this requirement, so you can test with a SNAPSHOT version if you want instead.
Colm. On Wed, Jun 4, 2014 at 12:58 PM, roband915 <[email protected]> wrote: > Ok "we've" misinterpreted the ws-trust functionality some. > With the configuration in place it now looks like there's some kind of > problem parsing the wsdl from ADFS2. This we have seen before and the > exception is correct. The wsdl that ADFS generates is a bit faulty I > believe. > > The error is "sp:KeyValueToken/wsp:Policy must have a value". > > Is this the actual error or are there still some configuration missing? Can > this parsing-error be "fixed" by cxf? > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5744685.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
