Can a FormsAuthenticationTicket survive an app poo

Question

I am looking for a solution where we can make a FormsAuthenticationTicket (and corresponding cookie) with a very long expiration period. This is possible by setting a high value or using a sliding expiration, but when the application pool of the website is recycled, the FormsAuthenticationTicket disappears (I think), the cookie gets invalid and the user is asked to login again.

Is there any way around this?

Answer 1

Set static machineKeys instead of the auto generated. This way the FormsAuthenticationTicket will survive app pool recycling.