glide.integrations.active.session.life_span sys_property clarity

William Jones2
Tera Contributor

yesterday

Hello,

 

I have a directive to enact the suggestions made on my impact scorecard 

 

When I go to update the glide.integrations.active.session.life_span property we had it set to 0 ( never expire) and we need to change it an actual value to be in compliance.

 

The documentation states 

 

"This configuration will enforce max life-span on active integration http sessions irrespective of inactive timeout"

 

It specifically states that its for active inte gration http sessions. 

 

So, for testing I go to set a value under the assumtion its for intergration api calls processing as guest.  This is clearly not the case because I get an error telling me that I need to set it to an equal or higher value than "glide.integration.session_timeout" which in my tainted instance is set to 360 because of some crazy stuff going on with our mobile app

 

All that aside I said ok for now ill mirror it to 360 so at least we have a value greater than 0..... 

 

When I save it tells me:

 

(i)Info Message

Any user session, regardless of activity, will expire after 360 minutes.
 
So I have to conclude that this is not for integrations only and applies to all user sessions? 
 
My main question is.... How can we make this more granular? I clearly need integration/guest sessions on a low time out. Mobile on a medium length timeout ( field techs) and my web sessions to be much longer... We have a 24 hour service desk where agents work 4x10h so I dont really want to terminate their sessions mid shift or in the middle of a call..... What have you all done for this?
0 Helpfuls
  • 476 Views
1 REPLY 1

William Jones2
Tera Contributor

yesterday

Is the info message just misleading?  we can set different session durations for these different user sessions 

 

glide.integrations.active.session.life_span

 

this doesnt impact all sessions like the message appears ?

0 Helpfuls