由网友(情深已故)分享简介：我有一个域名，如 http://www.mydomain.com ，我有multple域名指向在IIS中定义主机头，如 http://www.myONEdomain.com ，同一位置的 http://www.myTWODomain.com 等。I have one domain such as http://www...

我有一个域名，如 http://www.mydomain.com ，我有multple域名指向在IIS中定义主机头，如 http://www.myONEdomain.com ，同一位置的 http://www.myTWODomain.com 等。

I have one domain such as http://www.mydomain.com and I have multple domains pointing to the same location in IIS by defining host headers, such as http://www.myONEdomain.com, http://www.myTWODomain.com, etc.

在code我用Request.Url.Host确定哪些URL中的用户来自然后我采取不同的每一页基于域。

In the code I use Request.Url.Host to determine which url the user came from and then I act differently in each page based on the domain.

然而，如果用户在www.mydomain.com登录时，他们还需要访问myONEdomain，myTWOdomain等

HOWEVER, if the user logs in at www.mydomain.com, they also need access to myONEdomain, myTWOdomain, etc.

有谁知道我可以在.NET认证达致这？

Obvisously，从第一个域的登录工作正常，但只要用户点击了他们重定向到其他域的链接，有一些功能，他们无法这样做，因为在 IsAuthenticated 方法返回false。

Obvisously, the login from the first domain works correctly, but as soon as the user clicks on a link that redirects them to a different domain, there is some functions that they are unable to do because the IsAuthenticated method returns false.

我希望我说明了情况良好，这是有道理的，如果不是请询问。

I hope I explained the situation well and that it makes sense, if not please ask.

在此先感谢！

推荐答案

讽刺的是我碰到一个相当庞大的这个文件就在昨天就来了。我个人使用一个场景API背后传递来自主登录门户的姊妹网站会话，但这种解释的过程很详细：

Ironically I came across a rather extensive document of this just yesterday. I personally use a behind the scene API to pass a session from the main login gateway to sister sites, but this explains the process in great detail:

HTTP：//www.$c$cproject.com/KB/ ASPNET / CrossDomainSSOExample.aspx