On Tuesday, September 06, 2011 1:35:57 PM samyem wrote: > Thanks for the quick reply. I've actually done clean builds and the problem > persists.
Has nothing to do with clean builds... What I'm suggesting is to grab the WSDL from the service and clean out any policies in there so you start with a straight WSDL without and WS-Policy fragments in it. If you start from that, you may at least get the NTLM auth stuff working. Dan > I think I am missing some critical pieces here dealing with > WS-SecurityPolicy for NtlmAuthentication that arise from the WCF's binding. > Using either clientCredentialType="Ntlm" and clientCredentialType="Windows" > does not work and CXF complains about having no assertion builder for the > corresponding types. > > Since then I've attempted to use the WCF Express Interop library at: > http://wcf.codeplex.com/wikipage?title=WCF%20Express%20Interop%20Bindings > http://wcf.codeplex.com/wikipage?title=WCF%20Express%20Interop%20Bindings > and tried to use the wso2InteropBinding and metroBinding but both does not > seem to work. With wso2InteropBinding and clientCreditialType="Windows" the > assertion builder was looking for NtlmToken and it failed on that. > > Now I'm trying to see if the code at > http://svn.apache.org/repos/asf/cxf/sandbox/interopfest is going to be any > help but I have not yet found an example that works against Windows/NTLM > authentication, which is what I'm looking for. > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/NTLM-security-between-WCF-and-CXF-tp4763671 > p4775972.html Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
