How to extend the time that the system logout the user and then he needs to reconnect again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2024 04:10 AM
Hi,
How to extend the time that the system logout the user and then he needs to reconnect again?
Thanks, Shir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2024 04:38 AM
In ServiceNow, you can extend the session timeout duration by adjusting the session timeout settings. Here's how to do it:
1. Navigate to System Properties: Go to the "System Properties" module in the ServiceNow instance.
2. Search for 'Session Timeout': Use the search bar or scroll down to find the property named "glide.ui.session_timeout".
3. Modify the Session Timeout Value: Update the value of "glide.ui.session_timeout" to the desired session timeout duration. The value is in seconds, so set it to the number of seconds you want before the session expires.
4. Save Changes: Save your changes to apply the new session timeout setting.
By extending the session timeout duration, users will remain logged in for a longer period before being automatically logged out and prompted to reconnect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2025 06:57 PM
Hi nirajjoshi,
Would you happen to know where we can set up the prompted to reconnect pop up? Our portal is missing this after session timeout.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2024 05:17 AM
Hello @Shir Sharvit
This is controlled by system property glide.ui.session_timeout
The default value is 30 minutes.
Please mark the answer as helpful and correct if helped.
Kind Regards,
Ravi Chandra.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2024 05:41 AM
Use the glide.ui.session_timeout property to designate, in minutes, activity timeout value.
- The longer the specified session time-out, the greater the amount of memory is utilized during a processing session. The base system uses a default Apache Tomcat timeout duration of 30 minutes.
- The Now Platform still logs out users out with Remember Me. After 30 minutes of inactivity in the application, the platform logs the user out automatically, unless the Remember Me check box in the login page is selected. What ’s different is that they don’t log in again to continue.
- If there are gauges or content on users' home pages that refresh automatically, then this timeout may never be reached.
More information
Property name | glide.ui.session_timeout |
Configuration type | System Properties (/sys_properties_list.do) |
Configure in Instance Security Center | Yes |
Purpose | To enforce session timeout. |
Recommended value | User specified timeout in minutes. 30 minutes is the recommended value, but this value may vary depending on functionality and security requirement. Do not set this value to more than one day. |
Functional impact | (Medium) This remediation enforces timely expiration of user account. No functionality impact, however User experience is altered. |
Security risk | (Medium) User sessions being active for indefinite amount of time is a security risk and should expire on a time-based configuration. |
References | |
Please mark the answer as helpful and correct if helped.
Kind Regards, Amit Pandey |
|
|