If you are seeing that value for the initial WS-MEX call from the client to the STS, then you can change it to use the SOAP 1.2 namespace by adding the following jax-ws property:
<entry key="ws-security.sts.client-soap12-binding" value="true"/> Colm. On Mon, Jun 16, 2014 at 8:41 AM, roband915 <[email protected]> wrote: > I suspected that it could have been just that. I removed the entry > "ws-security.sts.client" with all its configuration as a start from my > jaxws:client-configuration and now the client really tries to create a > requestsecuritytoken-request. The problem now is the soap-version. My wsdl > uses soap 1.2. > > On both the client and the server I added the following configuration: > <jaxws:binding> > <soap:soapBinding version="1.2" /> > </jaxws:binding> > > Still in the logs I can see the following: > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> > > What's missing? Why does cxf insist of using an old namespace for soap? > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745190.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
