Running AWX 1.0.6.23 in an OpenShift pod.
The documentation (https://docs.ansible.com/ansible-tower/latest/html/administration/authentication_timeout.html) says that Settings → System → Idle Time Force Log Out controls the browser session expiration (the way I understood). My setting is default = 1209600, which is 336 hrs. However, if I leave the browser idle for some time - feels like under an hour - I come back to “Your session timed out due to inactivity. Please sign in.”
What am I missing? Browsing through the code, I don’t see a clear setting that control the cookie / expiration, so looking for help here.
Hello,
Currently, in 1.0.6.23, the register method for SESSION_COOKIE_AGE seems to be missing; so changing this in the UI, like you tried, is consequentially broken. We are working on fixing this.
Thanks,
Christian
Thank you, Christian. I assume, there is an alternative way changing the current low default somewhere in the code (but not through the configuration). I guess, considering that requires the process restart in the container and will go away on redeploys, will wait till the UI is fixed. Not a huge issue.
I’m still experiencing this issue with 1.0.6.41. I’ve checked the Postgres db, settings.py, and the value via the API, and they all agree on SESSION_COOKIE_AGE=1209601. Yet if I set my clock forward 30 minutes (or wait for 30 real-time minutes to pass), my session is expired. The expiry date for the sessionid cookie in browser is even properly 2 weeks in the future, so I’m at a loss for where this 30 minute timeout is coming from.
Hi nlopez,
Thanks for pointing this out. This has been fixed by this commit (https://github.com/ansible/awx/commit/ae0793f3744f78a0826795ceea3bfe9625a61d70) and supported completely in the UI in a related commit. If you pull the latest awx code, you should be good to go.
Thanks,
Christian