J
John Saunders
I have an existing ASP.NET 1.0 application at the root of a web site. There
is another 1.0 application in a virtual directory under the root. Forms
Authentication works fine between the two.
When the script maps in the sub-application are changed to use ASP.NET 1.1,
Forms Authentication breaks. In particular, the Forms Authentication cookie
no longer decrypts, so that the AuthenticateRequest handler finds
Request.IsAuthenticated == false. No other changes are made to the
sub-application, which was not recompiled for Framework 1.1, and resetting
the script maps to use ASP.NET 1.0 restores full functionality.
Setting both the root application and the sub-application to use ASP.NET 1.1
also allows the cookie to be decrypted properly.
Both applications have an explicit <machineKey> element in their web.config
files.
We are not ready to upgrade all of our applications to use ASP.NET 1.1. Does
anyone have a solution for this, or any ideas of where I should go from
here?
Thanks,
John Saunders
is another 1.0 application in a virtual directory under the root. Forms
Authentication works fine between the two.
When the script maps in the sub-application are changed to use ASP.NET 1.1,
Forms Authentication breaks. In particular, the Forms Authentication cookie
no longer decrypts, so that the AuthenticateRequest handler finds
Request.IsAuthenticated == false. No other changes are made to the
sub-application, which was not recompiled for Framework 1.1, and resetting
the script maps to use ASP.NET 1.0 restores full functionality.
Setting both the root application and the sub-application to use ASP.NET 1.1
also allows the cookie to be decrypted properly.
Both applications have an explicit <machineKey> element in their web.config
files.
We are not ready to upgrade all of our applications to use ASP.NET 1.1. Does
anyone have a solution for this, or any ideas of where I should go from
here?
Thanks,
John Saunders