- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How to set idle time, when the user has no activity for a long time, for example 15 minutes, then splunkweb will ask to log in again
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi @imam29
Just to check, have you restarted Splunk since making this change?
Its also worth considering the following from the docs - How long did you wait to check for a timeout? What is your tools.sessions.timeout set to?
The countdown for the splunkweb/splunkd session timeout does not begin until the browser session reaches its timeout value. So, to determine how long the user has before timeout, add the value of ui_inactivity_timeout to the smaller of the timeout values for splunkweb and splunkd. For example, assume the following:
splunkweb timeout: 15m
splunkd timeout: 20m
browser (ui_inactivity_timeout) timeout: 10m
The user session stays active for 25 minutes (15m+10m). After 25 minutes of no activity, the session ends, and the instance prompts the user to log in again the next time they send a network request to the instance.
Please let me know how you get on and consider adding karma to this or any other answer if it has helped.
Regards
Will
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
after we add tools.sessions.timeout , it is work
Thank you
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
where is setting splunkweb timeout and splunkd timeout ? we only set in web.conf
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

HI @imam29
In this case, I would expect the timeout to be after 30 minutes of no activity in the UI.
The other timeout option is in server.conf/[general]/sessionTimeout -
The ui_inactivity_timeout is the amount of minutes when there is no user interface clicking, mouseover, scrolling, or resizing. * Notifies client side pollers to stop, resulting in sessions expiring at the 'tools.sessions.timeout' value, so any mouseover, scrolling etc on the browser will reset this timer.
Just to check, have you restarted since making these changes?
Please let me know how you get on and consider adding karma to this or any other answer if it has helped.
Regards
Will
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi @imam29
It sounds like you'll need to update the ui_inactivity_timeout setting under web.conf/[settings] which is the timeout for when the user does not interact with the browser, but there is also another setting "tools.sessions.timeout" which is the actual session timeout value.
However, I think it would be worth reading this doc about setting session timeout so that you can satisfy yourself that you are updating the correct setting and not being overly permissive with timeouts.
In addition to managing in the config files, you can also update this in the UI if preferred:
- Click Settings in the upper right-hand corner of Splunk Web.
- Under System, click Server settings.
- Click General settings.
- In the Session timeout field, enter a timeout value.
- Click Save.
Please let me know how you get on and consider adding karma to this or any other answer if it has helped.
Regards
Will
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I has been configure ui_inactivity_timeout = 15 but not working , the session still there not ask login again
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi @imam29
Just to check, have you restarted Splunk since making this change?
Its also worth considering the following from the docs - How long did you wait to check for a timeout? What is your tools.sessions.timeout set to?
The countdown for the splunkweb/splunkd session timeout does not begin until the browser session reaches its timeout value. So, to determine how long the user has before timeout, add the value of ui_inactivity_timeout to the smaller of the timeout values for splunkweb and splunkd. For example, assume the following:
splunkweb timeout: 15m
splunkd timeout: 20m
browser (ui_inactivity_timeout) timeout: 10m
The user session stays active for 25 minutes (15m+10m). After 25 minutes of no activity, the session ends, and the instance prompts the user to log in again the next time they send a network request to the instance.
Please let me know how you get on and consider adding karma to this or any other answer if it has helped.
Regards
Will
