Re: Forms Authentication problem. Keep looping back to logon page

From: [MSFT]Allen (yweng_at_online.microsoft.com)
Date: 04/30/03


Date: Wed, 30 Apr 2003 09:52:08 GMT


The workaround has been given in the article at
http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx

"Configure an explicit key in a local web.config or in machine.config or
remove the ˇ°IsolateAppsˇ± modifier from the attribute. With the modifier
removed, the .NET Framework version 1.0 behavior will be identical. Note
that only applications that want to share forms authentication cookies
across applications are affected by this change."

Thanks,
-Allen

Disclaimer:
This posting is provided "AS IS" with no warranties, and confers no rights.
Got .Net? http://www.gotdotnet.com

--------------------
| From: "Per Schjetne" <per.schjetne@dmhuset.no>
| References: <eZJr544ADHA.1600@TK2MSFTNGP10.phx.gbl>
<tzlxIV$ADHA.2172@cpmsftngxa06.phx.gbl>
| Subject: Re: Forms Authentication problem. Keep looping back to logon page
| Date: Tue, 29 Apr 2003 10:11:06 +0200
| Lines: 99
|
| I have the same problem but I really want to use the 1.1 framework instead
| of 1.0. I have started from scratch on a clean 1.1 installation but I
can't
| make it work. I can't find any formsauthentication-samplecode for this
| version. Can you help?
|
|
|
| "[MSFT]Allen" <yweng@online.microsoft.com> wrote in message
| news:tzlxIV$ADHA.2172@cpmsftngxa06.phx.gbl...
| > The 1.1 Framework is designed to be highly compatible with the 1.0
| > Framework. The vast majority of 1.0 applications can work equally well
| with
| > the Framework 1.0 or 1.1. Only in the rare event does a 1.0 application
| > does not work on the 1.1 Framework. If you ran into the problem, you can
| > configure the application to only support the 1.0 Framework.
| >
| > The installation of the version 1.1 Framework automatically adds the 1.1
| > ASP.NET filter to the filter list on the Web server's root Web site.
| > Updating the filter at the root level causes all sites that are not
| > individually configured to start using the 1.1 version of the Framework.
| > Any site that needs to continue to use the 1.0 Frameworks needs to be
| > individually configured to use the 1.0 ISAPI filter. The configuration
of
| > the ISAPI filter can only be at the Web site level. Individual VRoots
| > cannot be configured to use a different ISAPI filter. You can do it in
IIS
| > Admin console.
| >
| > On gotdotnet, you will find more detailed information about changes
| > introduced in .NET 1.1. Please take a look at
| >
| > 1. Backwards Breaking Changes from version 1.0 to 1.1
| > http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx
| > 2. Compatibility Considerations and Version Changes
| > http://www.gotdotnet.com/team/changeinfo/default.aspx.
| >
| > I noticed this item in the first article
| > "autogenerated ASP.NET forms authentication and viewstate keys are now
| > isolated per application by default. "
| >
| > Affected APIs:
| > The ASP.NET Forms authentication feature as a whole when using
| > autogenerated keys. This includes:
| > FormsAuthentication.RedirectFromLoginPage // all
| > FormsAuthentication.SetAuthCookie // all
| > FormsAuthentication.GetAuthCookie // all
| > FormsAuthentication.Encrypt // all
| > FormsAuthentication.Decrypt // all
| >
| > It seems addressing the same issue as yours.
| >
| > HTH,
| > -Allen
| >
| > Disclaimer:
| > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| > Got .Net? http://www.gotdotnet.com
| >
| > --------------------
| > | From: "Horace Paulk, Jr." <hpaulk@johnseastern.com>
| > | Subject: Forms Authentication problem. Keep looping back to logon page
| > | Date: Tue, 15 Apr 2003 16:33:55 -0400
| > | Lines: 29
| > |
| > | I get the Login screen to work correctly and it generates the
| > authentication
| > | cookie.
| > |
| > | However, when I go to the next form that should use the same
| > authentication
| > | cookie it redirects me back to the logon page. It is acting like it
| isn't
| > | seeing the authentication cookie.
| > |
| > | web.config....login page
| > | <authentication mode="Forms">
| > | <forms name="TESTAUTH" loginUrl="/Startup/Login.aspx"
| > | protection="All" timeout="120" path="/"
| > | requireSSL="false" slidingExpiration="false">
| > | </forms>
| > | </authentication>
| > | <authorization>
| > | <deny users="?"/>
| > | <allow users="*"/>
| > | </authorization>
| > |
| > | web.config....other form same as above
| > |
| > | have version 1.1 and 1.0 of net framework.
| > |
| > | If I remove 1.1 and the requireSSL and sliding expressions.
everything
| > | works correctly.
| > |
| > | any suggestions will be greatly aprreaciated.
| > |
| > |
| > |
| >
|
|
|



Relevant Pages

  • Re: Forms Authentication problem. Keep looping back to logon page
    ... I have the same problem but I really want to use the 1.1 framework instead ... > ASP.NET filter to the filter list on the Web server's root Web site. ... > individually configured to use the 1.0 ISAPI filter. ... > "autogenerated ASP.NET forms authentication and viewstate keys are now ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • RE: Forms Authentication problem. Keep looping back to logon page
    ... The 1.1 Framework is designed to be highly compatible with the 1.0 ... ASP.NET filter to the filter list on the Web server's root Web site. ... individually configured to use the 1.0 ISAPI filter. ... The ASP.NET Forms authentication feature as a whole when using ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: II6.0 ISAPI & MIME types
    ... "Ken Schaefer" wrote: ... site uses forms authentication mode, ... What is the difference between MIME types & ISAPI filter. ...
    (microsoft.public.inetserver.iis.security)
  • RE: 802.1x RADIUS Deployment in Wireless LAN
    ... To talk about WPA in Wi-Fi Alliance's ... EAP in combination with 802.1X is used for Authentication. ... or use Pre-shared keys (typically in homes where you can't have a RADIUS ... such features need to be built on the cards as the cards use these features ...
    (Security-Basics)
  • how to jump start a brand new website (under the gun)
    ... basic user authentication (using php sessions/cookies to maintain authentication) ... knowing how quickly they wanted something they could look at, i initially suggested using a framework such as mambo or seagull, but they don't want to have to deal with the scalability issues and other restrictions of those types of tools (issue is closed at this point, so no need to argue scalability of these types of CMS frameworks. ...
    (comp.lang.php)