On Monday, July 16, 2012 09:50:40 AM Gina Choi wrote: > Colm and Glen, > > Thanks for your responses. I think that you two suggest two different > solutions. One is supporting both 1.1 and 1.2 and the other is supporting > solely 1.2.
Note that with CXF, a 1.2 endpoint will also handle 1.1 requests just fine. The 1.2 endpoint will detect a 1.1 request and respond with the appropriate 1.1 based response. Thus, you just need to deploy a 1.2 endpoint and it should be able to handle both types of clients fine. Dan > > Colm: > <<< > You need to add an endpoint to the STS WSDL that uses a SOAP 1.2 binding. > > So, I need to add another endpoint in ws-trust-1.4-service.wsdl file like > bellow? Do I need to create UTEncrypted_Binding in similar way? > > <wsdl:service name="SecurityTokenService"> > > <wsdl:port name="UTEncrypted_Port" > binding="tns:UTEncrypted_Binding"> > > <soap:address location="http://localhost:8080/jaxws-sts/sts"; /> > > </wsdl:port> > > <wsdl:port name="UTEncrypted_Port12" > binding="tns:UTEncrypted_Binding"> > > <soap12:address location="http://localhost:8080/jaxws-sts/sts"; /> > > </wsdl:port> > > > Glen: > <<< > I ran the CXF STS on SOAP 1.2 endpoints before when testing > interoperability with Metro. It should work, the WSDL will just need some > modifications > (http://www.jroller.com/gmazza/entry/switch_soap11_to_soap12). > > I changed wsdl file from 1.1 to 1.2 based on your tutorial in the past. My > Java client to Fediz STS is fine with 1.1. If I change wsdl file to 1.2, > my CXF client will be automatically generate 1.2 message to communicate > with 1.2 end point? > > Thanks. > > Gina -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
