References to sessions (records in the SecurityContext table) are currently stored server-side. Consequently, when the server reboots, or an application is updated, all user sessions are lost. Instead, if the reference is stored in a cookie (on the client side), the session would survive application updates and I could safely update applications.

Submitted by Sander Vermolen on 10 February 2010 at 12:01

+1

I have to log into researchr and yellowgrass almost every day I use it. If this would fix it, I’m all for it!