共享窗体身份验证并不.NET 3.5和.NET 4.0应用程序之间的工作 [英] Shared Forms Authentication not working between .NET 3.5 and .NET 4.0 applications

查看:170
本文介绍了共享窗体身份验证并不.NET 3.5和.NET 4.0应用程序之间的工作的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有两个Web应用程序,NET 3.5的运行下一个,另一个已经升级到.NET 4.0。在升级之前,共享验证是设置和MSDN文章中指出的两个应用程序之间正常工作:

I have two web applications, one running under .Net 3.5, the other has been upgraded to .Net 4.0. Prior to the upgrade, shared authentication was setup and working correctly between the two applications as indicated in the MSDN article:

http://msdn.microsoft.com/en-us/library/ eb0zx8fc.aspx

3.5应用程序是根据经典.NET程序池(2.0版,经典管道)上运行。

The 3.5 Application is running under the Classic .NET AppPool (v2.0, Classic Pipeline).

4.0应用程序下的ASP .NET 4.0版的应用程序池(V4.0,综合管线)上运行。

The 4.0 application is running under the ASP .NET v4.0 AppPool (v4.0, Integrated Pipeline).

推荐答案

原来,这个问题是应用程序池的.NET 3.5应用程序下运行。我们切换应用程序池,以ASP .NET v4.0的经典(但不升级应用程序本身来在4.0 / VS2010运行)。

The problem turned out to be the App Pool the .NET 3.5 application was running under. We switched the app pool to ASP .NET v4.0 Classic (without upgrading the application itself to run under 4.0 / vs2010).

共享认证是恢复正常。我找不到此列为要求任何地方,所以希望这将节省别人一些时间在未来。

Shared authentication is back to normal. I could not find this listed as a requirement anywhere so hopefully this will save someone else some time in the future.

这篇关于共享窗体身份验证并不.NET 3.5和.NET 4.0应用程序之间的工作的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆