The automatic log out period for Commander® users and Service Portal users is configurable. These session timeouts are a security measure that define how long Commander® remains available during a period of inactivity before the user is logged out. As long as a user is working with the system within the specified time, Commander® will not log off the user.
Configuring Session Timeouts
To view or edit current session timeout settings:
- From the Configuration menu, choose System Configuration.
- Switch to the Authentication tab.
- Click Edit under Session Preferences.
- Enter a value in seconds, minutes or hours for Commander and/or the Service Portal and click OK.
Troubleshooting Session Timeouts
Once you have confirmed the system settings by following the procedure above, if you are still being logged out earlier than expected, try the following steps to see if they correct the situation.
- Close all browser windows.Having multiple browser windows open can sometimes cause issues with separating user sessions. You may be getting logged off appropriately for another session you have open without realizing it. After all browsers have been closed, open a new browser window and see if the behavior can be reproduced.
- Clear your browser cache.Sometimes data cached by your browser can lead to early triggering of session timeouts with cloud applications. Refer to the browser vendor's help files for more information about how to clear the cache. Alternatively, running a program like Piriform's CCleaner will handle this operation for all installed browsers at once.
- Check your system time.Sometimes, having a system time that is not synchronized with either Commander's application server, the Domain Controller, or both can result in unusual behavior from applications. Compare the system time, and if there is a difference greater than 2 minutes, speak with your network administrator.
Related Articles
Capture web session traffic in a HAR file for troubleshooting 495Number of Views Inventory imports may be reported as failing or timing out after Flexera One ITAM 2024 R2.2 update 6Number of Views Cognos Error: Missing required credentials for authentication. Or the session might be timed out. 10Number of Views Controlling Commander logging level 329Number of Views Active Directory data may not be updated due to the import process for .actdir files timing out (or taking a long time) at… 8Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago