I am having an ongoing problem with my users being unable to stay logged in for more than 10 minutes (in a DNN 5.1.1 install). This problem seems to have emerged when I migrated from .net 2.0 to .net 3.5. Previously it was not a problem - users who selected the 'Remember me' tick box would stay logged in for 7 days (as per the settings I have for PersistentCookieTimeout in web.config, which have not been changed with the migration to .net 3.5, however now the PersistentCookieTimeout  parameter is now no longer being respected).

In terms of troubleshooting this I was thinking that maybe something in my install got corrupted. My thought was to upgrade from v5.1.1 to v5.1.4  but to use the install version of the DNN core - not the upgrade version. My thinking - probably flawed – is that the install version should by definition be more complete in terms of core files than the upgrade version.

Am I bonkers to consider upgrading with an install version? Is my thinking flawed?

Any advice would be greatly appreciated as I am very much at a loss about what I should to solve the Persistent Cookie Timeout problem.

Mitchel,

Thanks for the reply and the explanation of the differences between the install and upgrade versions.

With the help of the Firefox "Firebug" plugin I was able to see the following cookies after logging in with a (non-admin, non-host) user id:

• portalroles - has expiration 1 minute later than the time I logged in.
• portalaliasid - has expiration 1 minute later than the time I logged in.
• .DOTNETNUKE - has expiration 7 days later than the time I logged in.
• DotnetnukeAnonymous - has expiration 19minutes 55 seconds later than the time I logged in (the 5 seconds short of 20 mins may correpsond to the time it took between me hitting the DNN login page and me logging in, no?)

When I move to another page the expiration on .DOTNETNUKE and the DotnetnukeAnonymous cookies stays the same. However the portalroles and portalaliasid are updated to have a new expiration of 1 minute after I hit the "just-visited" page.

I also see:

• three ASPSESSIONID* cookies (where the * is a different 8 character string for each of the 3 cookies. The expiration for these 3 = "Session")
• one .ASPXANOYMOUS cookie, expiration of 12 Jan 2010
• language cookie - expiration = "Session"

Does any of the above help zoom in on the problem?

Many thanks.

Based on this then, the user is actually logged in for 20 minutes, THEN they are logged out, and the "Remember Me" function just isn't working.  Is this a correct assumption?