连接到经过身份验证的下游netTcp端点的问题 [英] Problems connecting to an authenticated downstream netTcp endpoint

问题描述

在相关的帖子中，我无法连接到basicHttp端点，似乎是由于连接到下游服务时WCF模拟问题所致.有趣的是，当我用ASMX Web服务替换basicHttp WCF服务时，它可以正常工作.这两个服务都使用ASP.NET web.config文件中的<identity impersonate="true" userName=".." password=".." />，但是ASMX服务可以工作，而basicHttp WCF服务则不能.

In a related post, I am having trouble connecting to a basicHttp endpoint and it seems that it is due to WCF impersonation issues when connecting to a downstream service. The funny thing is that it works fine when I replace the basicHttp WCF service with an ASMX web service. Both services use <identity impersonate="true" userName=".." password=".." /> from ASP.NET web.config file, but the ASMX service works while the basicHttp WCF service doesn't.

如果ASP.NET和WCF之间存在Kerberos委派问题，这似乎可能是某种形式吗?
还是我可以在WCF配置中添加一些东西来传递这个模拟用户(请注意我正在使用框架4，所以我目前几乎没有配置)?

Does this seem likely to be some sort if Kerberos delegation issue between ASP.NET and WCF?
Or is there something that I can add to my WCF configuration to pass this impersonated user (note I am using framework 4, so I currently have almost no configurtation)?

推荐答案

最后得出结论，我需要将<serviceHostingEnvironment aspNetCompatibilityEnabled="true"/>添加到web.config文件的WCF部分，并添加一个中定义的凭据调用下游netTcp端点.

Finally worked out that I needed to add <serviceHostingEnvironment aspNetCompatibilityEnabled="true"/> to the WCF part of the web.config file, and an AspNetCompatibilityRequirementsMode attribute to the implementation of the basicHttp endpoint. This will then call the downstream netTcp endpoint using the credentials defined in <identity impersonate="true" userName=".." password=".." />.

这篇关于连接到经过身份验证的下游netTcp端点的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！