Captive portal and Android cookies: How are cookies stored that are delivered from captive portal?

[ericgearhart]

First, some background. We have captive portal configured and we have a "BYOD" wireless network. We have the cookie lifetime in Palo Alto set to one week.

For our Android users, it seems that once they get redirected to the captive portal and authenticate, if they get out of the web browser app and let their phone sleep, they lose the cookie that PA delivered. They have to reauthenticate basically, when we have deliberately tried to have their cookie last for a week.

I understand that on the backend Android device, cookie persistence seems to be in-memory, and there's a good discussion about it on Stack Overflow:

http://stackoverflow.com/questions/4082799/android-how-to-store-cookies

Does anyone know of any workarounds for this? It seems like some Android cookies I receive can persist and don't "live in memory" so to speak, because some sites I log into on my phone always remember who I am and my cookie persists no matter what I do (LinkedIn.com is an example)

[ericgearhart]

Here's my session cookie persistence settings by the way:

[bmiles]

Having the same problem. Looking for an answer.