Session Timeout settings inqury

joymorales
Giga Guru

Hi Team.

 

We just upgraded to Tokyo and to the Next Experience.  We are also setup for Azure AD idp for SSO.

We are seeing that our ITIL sessions timeout in 30 minutes, where as in the Rome release, they did not.  I looked on the web and found that the glide.ui.session_timeout system property controls the session timeouts.  However, we don't have this system property on our list.  We see glide.guest.session_timeout (30 mins), glide.sso.acr.ui.session.timeout (30 mins) (account recovery) and glide.ui.session_timeleft (2 mins), but we do not see the glide.ui.session_timeout one.

 

I cannot tell which current property is controlling our session timeout.  Should I create a new property for the glilde.ui.session_timeout?  Any way to set the timeout to never timeout for us technicians?

 

Any information that you can provide will be greatly appreciated.

Thank you!

2 REPLIES 2

Brad Bowman
Kilo Patron
Kilo Patron

You should have/create glide.ui.session_timeout with the Type of integer.  It's defaulting to 30 minutes in lieu of a property to tell it otherwise.  The out of the box one on a fresh instance has the Description "Sets the session timeout, in minutes. Values exceeding 1440 minutes will be treated as one day."  I have this set to 1441 on my PDI, and that's as close as you can get to never timing out.  Note that this will apply to every user.

Hi,

We are having an issue with timeout settings in Tokyo patch 3.  When we have multiple SN instances/tabs opened in Chrome the 'extend' (warning) does not extend across to all tabs so a user will inevitably get logged out of their inactive session in one tab though they remain active in another.  Has this been reported before?