Hello,
Ugh - I love WCF, but resolving issues like this is soooo painful... :)
IMHO configuring security for WCF is the most complex part of the whole
process! Anyway, on to your problem...
I've had similar issues like this before, and my gut feeling is that it is
something to do with the version of Xml web services that InfoPath uses to
communicate with web services. It seems to be great for the "simple" stuff,
but as you found out when you add authentication in it just doesn't seem to
play nicely. I don't really have any solution to offer I'm afraid, but some
of the following might help:
- InfoPath 2007 uses Microsoft XML Core Services v5 - the latest version if
v6. There is no way to upgrade AFAIK, but this may be causing an issue
somewhere
- Check the article on InfoPath web services support
(http://msdn2.microsoft.com/en-us/library/bb852081.aspx#ipOverviewWebServiceSuppo
rt_WebServiceRequirementsandLimitations)
to make sure your web service is OK with InfoPath. There may be an issue
with the authentication requirements, but looking through the article I can't
see anything that might be the cause, especially seeing as it works in your
test application. I may have missed something though
- basicHttpBinding (http://msdn2.microsoft.com/en-us/library/ms731361.aspx)
is usually used with "older" style web services (like .asmx web services).
wsHttpBinding might help out here
(http://msdn2.microsoft.com/en-us/library/ms731299.aspx) or perhaps even
webHttpBinding (http://msdn2.microsoft.com/en-us/library/bb412176.aspx).
wsHttpBinding in particular offers more security-related information with
InfoPath might be happier to consume.
The only InfoPath -> WCF integration I've done used very basic read-only
web services that were secured via a digital cert and IP address
restrictions. They were just dynamic look-up data with no real security
requirements hence very very simple. The config I used was basicHttpBinding.
HTH
Gavin.

Signature
2B | !2B
> Hello,
>
[quoted text clipped - 107 lines]
> Thanks in advance!
> Regards.
Darlan Jr. - 16 Apr 2008 14:32 GMT
Thanks a lot, Gavin. Your post put me in the right direction to solve my
problem.
The solution, for this specific issue, is just set the security binding
configuration as the following code:
<bindings>
<basicHttpBinding>
<binding name="BasicHttpBinding_IContent">
<security mode="TransportCredentialOnly" >
<transport clientCredentialType="Windows"/>
</security>
</binding>
<binding name="BasicHttpBinding_IContentMT">
<security mode="TransportCredentialOnly" >
<transport clientCredentialType="Windows"/>
</security>
</binding>
</basicHttpBinding>
<wsHttpBinding>
<binding name="WSHttpBinding_IContent">
<security mode="Transport">
<transport clientCredentialType="Ntlm"/>
</security>
</binding>
<binding name="WSHttpBinding_IContentMT">
<security mode="Transport">
<transport clientCredentialType="Ntlm"/>
</security>
</binding>
</wsHttpBinding>
</bindings>
Gavin McKay - 16 Apr 2008 15:16 GMT
Good to have a result! InfoPath + WCF information is very rare
unfortunately...
So from your config you have changed the clientCredentialType to "Windows"
instead of "Ntlm" and that solved the problem? Nice!
Gavin.

Signature
InfoPath Knowledge Base
http://www.infopathkb.com/
2B | !2B
> Thanks a lot, Gavin. Your post put me in the right direction to solve my
> problem.
[quoted text clipped - 28 lines]
> </wsHttpBinding>
> </bindings>
michael.hncck@googlemail.com - 30 Apr 2008 18:00 GMT
I am experiencing the exact same problem, but your fix didn't work for
me! Are you running your WCF services on the same server as Forms
Services?