persistent formsauthentication

Discussion in 'ASP.NET / ASP.NET Core' started by steurm, Sep 6, 2003.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. steurm

    steurm

    I have a question about using FormsAuthentication and the option to create a persistent cookie. When logging onto my site, I use the FormsAuthentication to set a persistent cookie in order to 'remember' my login information the next time I enter the site.
     
    steurm, Sep 6, 2003
    #1
  2. steurm

    steurm

    Nobody with any ideas here ?

    I thought that authentication cookies were stored in the client browser, so it would be very strange that the functionality would change when the application is located on another server, or am I wrong here ?

    Any help would be greatly appreciated !

    Guy

    --
    Steurm
    www.steurm.net
     
    steurm, Sep 11, 2003
    #2
  3. Bruce

    Bruce DiscountASP.NET Staff

    Never seen that problem before.

    Try post your question to the ASP.net forum as well. (http://asp.net)

    quote:Originally posted by steurm

    Nobody with any ideas here ?

    I thought that authentication cookies were stored in the client browser, so it would be very strange that the functionality would change when the application is located on another server, or am I wrong here ?

    Any help would be greatly appreciated !

    Guy

    --
    Steurm
    www.steurm.net
    </blockquote id="quote"></font id="quote">
     
    Bruce, Sep 11, 2003
    #3
  4. Bruce

    Bruce DiscountASP.NET Staff

    Ok. We found the solution to the problem

    Change this setting in your web.config file

    <forms loginUrl="default.aspx" protection="All" timeout="15"/>

    to

    <forms loginUrl="default.aspx" protection="None" timeout="15"/>



    quote:Originally posted by steurm

    Nobody with any ideas here ?

    I thought that authentication cookies were stored in the client browser, so it would be very strange that the functionality would change when the application is located on another server, or am I wrong here ?

    Any help would be greatly appreciated !

    Guy

    --
    Steurm
    www.steurm.net
    </blockquote id="quote"></font id="quote">
     
    Bruce, Mar 15, 2004
    #4
  5. steurm

    steurm

    Thanks bruce, that does indeed the job !

    Do you know the reason why this needed to be altered, because with the old setting ("All") it worked locally.



    --
    Steurm
    www.steurm.net/steurm
     
    steurm, Mar 16, 2004
    #5
  6. Bruce

    Bruce DiscountASP.NET Staff

    I didn't figure this out, another of my collegue did.

    from what i understand, asp.net uses something in memory to decrypt the cookie content. when the site is recycle, that information is lost and asp.net will fail to decrypt and thus deny access.

    quote:Originally posted by steurm

    Thanks bruce, that does indeed the job !

    Do you know the reason why this needed to be altered, because with the old setting ("All") it worked locally.



    --
    Steurm
    www.steurm.net/steurm
    </blockquote id="quote"></font id="quote">
     
    Bruce, Mar 16, 2004
    #6
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page