集成 Windows 身份验证 - 对于互联网应用程序来说现实吗？
我正在阅读有关集成 Windows 身份验证有多么出色的内容，但只有很少的评论说它只适用于 Intranet。那么需要澄清的是，可以肯定地说这项技术对于互联网应用来说不现实吗？我正在开发一个与 SQL Server 连接的桌面应用程序，但我无法想象告诉所有客户按照我的规范在他们的家庭 PC 上配置 Windows 帐户。我是否错过了一些东西，因为这看起来很不现实。
（当然，如果 DBA 与 Intranet 上的用户关系密切，则情况不同。）
I'm reading about how wonderful Integrated Windows Authentication is, but there is only a few comments about how it's only good for intranets. So just to be clear, is it safe to say that this technology is not realistic for internet applications? I'm developing a desktop application that connects with SQL Server and I just can't imagine telling all my customers to configure a windows account on their home PCs according to my specifications. Am I missing somethimg because that seems quite unrealistic.
(of course, where the DBA has a close relationship with the users on an intranet, it's a different story.)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不得不说是的，Windows 身份验证最好留给 Intranet 应用程序 - 它非常适合需要在同一网络上进行的任何经过身份验证的通信。
听起来您想允许桌面应用程序（在您客户端的计算机上运行）直接与您的 SQL Server 对话？我强烈建议不要允许直接公共访问，尤其是当您无法将端口锁定到已知 IP 地址列表时。相反，请考虑在数据库和桌面客户端之间放置 WCF Web 服务。
I would have to say yes, Windows Authentication is best left to intranet applications - it's ideal for any authenticated communication that needs to take place on the same network.
It sounds like you want to allow the desktop app (running on your client's machine) to directly talk with your SQL Server? I would strongly recommend against allowing direct public access, especially if you cannot lock the port down to a list of known IP addresses. Instead, consider putting WCF Web Services between the database and the desktop client.