WCF 身份 NTLM Kerberos
我已经阅读了大量关于 WCF 客户端上客户端端点中的元素的帖子和文章,但我仍然有点困惑。我有一个客户端在尝试与 net tcp WCF 服务通信时收到 SSPI 错误。但是,当我将以下内容添加到配置中时,它工作正常。
<identity>
<servicePrincipalName />
</identity>
现在,根据我所读到的内容,这是告诉服务使用 NTLM 而不是 Kerberos。但是,我仍然不明白。
有谁能花点时间为我简单解释一下吗?那么,这里发生了什么,关于 NTLM 和 Kerberos 差异的一点背景知识,为什么它可以与其中一个一起工作而不是另一个,为什么这个元素不需要值,如何配置不需要的服务它以及为什么需要它?
谢谢
I have read numerous posts and articles about the element in client endpoints on a WCF client but I am still a little confused. I have a client which gets SSPI errors when attempting to communicate with a net tcp WCF service. However, when I add the following into the configuration it works fine
<identity>
<servicePrincipalName />
</identity>
Now from what I have read this is telling the service to use NTLM rather than Kerberos. However, I am still not getting it.
Does anyone have a few moments to explain this simply for me please. So, what is going on here, a little bit of background on the difference of NTLM and Kerberos, why it would work with one and not the other, why this element doesn't need a value, how to configure a service not to need it and why it is needed at all?
Thanks
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
以下是一篇博客文章,解释了 WCF 方面的 ntlm 与 kerberos:
http://blogs.msdn.com/ashishme/archive/2006/11/10/ntlm-vs-kerberos-windows-communication-foundation.aspx
Here is a blog post explaining ntlm versus kerberos with respect to WCF:
http://blogs.msdn.com/ashishme/archive/2006/11/10/ntlm-vs-kerberos-windows-communication-foundation.aspx