- ssh as root to the C2 server
- Edit /var/opt/cloudbolt/proserv/customer_settings.py
- add a line to the file:
- SESSION_COOKIE_AGE = 60 * 30 # 30 minute inactivity timeout
- That will set the user timeout in seconds. in this example the users will be logged out after 30 minutes of inactivity
- Restart apache: service httpd restart
TIP: To test that this is working, you could set the timeout to 2 seconds, ensure that you are auto-logged out very quickly after logging in, and then adjust the timeout to something appropriately higher.
Does this setting survive CloudBolt upgrades?
Yes, it does. The /var/opt/cloudbolt/proserv/customer_settings.py file is not altered during upgrades and the settings in there will still take effect afterwards.
Excellent, thank you Bernard!
Isn't this also caught by the setting on /admin/misc_settings/ called "inactivity timeout"?
They are related, but slightly different.
The SESSION_COOKIE_AGE will enforce a timeout from the server. So if the user hasn't made a request in that amount of time, their cookie will have expired and they will be asked to log back in the next time they try to load a page.
Thanks! It appears I need to make some changes to my customer_settings :)