经典ASP和放大器; ASP.Net认证 [英] Classic ASP & ASP.Net Authentication

问题描述

我有两个单独的应用程序（一个是传统的ASP，另一种是asp.net）其中，从用户的角度来看，应该​​无缝地为一体的应用程序的出现。正如其他人所指出的那样，两个应用程序不能共享会话信息，所以我打算沿着这些线路使用Windows身份验证： -

I have two separate apps (one is classic asp, the other is asp.net) which, from the point of view of the user, should appear seamlessly as one "application". As others have pointed out, the two apps can't share session information, so I am planning to use windows authentication along these lines:-

在ASP世界：

Request.ServerVariables("AUTH_USER")

和在ASP.Net（.NET 2.0）：

and in ASP.Net (.Net 2.0):

System.Threading.Thread.CurrentPrincipal.Identity.Name

这是从我的商业逻辑层被称为（即

which is called from my business logic layer (i.e.

HttpContext.Current.User.Identity.Name

不提供给我）。

这被认为是很好的做法还是有更好的办法？我需要什么考虑设置IIS时？

Is this considered good practice or is there a better way? What do I need to consider when setting up IIS?

推荐答案

我有一对夫妇几年前做到这一点，我记得斯科特·格思里已经让我开始，一个好的职位。

I had to do this a couple of years ago and I remembered Scott Guthrie had a good post that got me started.

<一个href=\"http://weblogs.asp.net/scottgu/archive/2007/03/04/tip-trick-integrating-asp-net-security-with-classic-asp-and-non-asp-net-urls.aspx\" rel=\"nofollow\">http://weblogs.asp.net/scottgu/archive/2007/03/04/tip-trick-integrating-asp-net-security-with-classic-asp-and-non-asp-net-urls.aspx

我们最终购买书他谈论过。这是一个很好看的。

We ended up buying the book he talks about too. It's a good read.

这篇关于经典ASP和放大器; ASP.Net认证的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！