在 SharePoint 中扩展 Web 应用程序时的安全问题
因此,我有一个正在运行的网站 (http://servername),并且想要添加另一个 URL http: newURL 来访问相同的内容。我希望两个站点使用相同的活动目录域进行用户/身份验证。
我扩展了现有的 Web 应用程序,以便新的 URL 可以工作。我将新区域的身份验证提供程序配置为与现有区域相同(NTLM 和 Windows 身份验证)。
问题是我无法使用上述安全设置通过新 URL 登录该网站。它一直显示访问被拒绝(IIS 访问被拒绝页面,而不是 SharePoint)。 它让我进入的唯一方法是如果我打开我不想做的基本身份验证......
我错过了什么? 我还尝试只编辑备用访问映射而不扩展 Web 应用程序,但这根本不起作用......
So, I had a site running (http://servername) and wanted to add another URL, http: newURL to get to the same content. I wanted both sites to use the same active directory domain for users/authentication.
I extended my existing web application so that the new URL would work. I configured the authentication provider for the new zone to be the same as my existing one (NTLM and Windows authentication).
The problem is that I can not log into the site via the new URL, with the above security settings. It keeps saying access denied (IIS access denied page, not SharePoint).
The only way it will let me in is if I turn on basic authentication which i do not want to do...
What am I missing?
I also tried to just edit the Alternate Access Mappings without extending the web application and that didnt work at all...
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
虽然这属于 serverfault.com,但我会在这里建议一个答案,并希望稍后可以转移这个问题。
看来您正在 Windows 中遇到环回检查。本质上,Windows 会阻止对主机名与本地计算机名称不匹配的 URL 的请求。如果您从另一台计算机连接到 SharePoint 网站,您会发现该请求有效。这是一项安全功能,旨在防止某些类型的攻击。
有关更多详细信息,请参阅这篇 Microsoft 知识库文章。
有两种方法可以解决此问题(有关这两种方法的详细信息,请参阅知识库文章):
完全,或
我通常在开发服务器上选择 1。
While this belongs on serverfault.com, I'll suggest an answer here and hope that this question gets moved later.
It looks like you're running into the loopback check in Windows. Essentially, Windows is blocking requests for URLs where the host name does not match the local computer name. You'll find that the request works if you connect to your SharePoint site from another machine. This is a security feature designed to prevent certain types of attacks.
See this Microsoft KB article for more details.
There are two ways to resolve this (see the KB article for details on both):
completely, or
I usually opt for 1 on a development server.