AWX User Browser Times Out in Less than an Hour

[stan.v...@exlhub.com]

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.

[Christian Adams]

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 

__________________________________________________

Christian M. Adams

Associate Software Engineer at Ansible - Red Hat

University of North Carolina at Chapel Hill, Class of 2014

cha...@redhat.com  |  (919) 218-5080  |  GitHub: rooftopcellist

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.
To post to this group, send email to awx-p...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/bc8c34bb-561e-45bb-a28d-290b4ec10063%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[stan.v...@exlhub.com]

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.

[nlo...@gmail.com]

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.

[Christian Adams]

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

__________________________________________________

Christian M. Adams

Associate Software Engineer at Ansible - Red Hat

University of North Carolina at Chapel Hill, Class of 2014

cha...@redhat.com  |  (919) 218-5080  |  GitHub: rooftopcellist

To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/e9846d91-cf21-4548-b472-32e884e39689%40googlegroups.com.