System Time Out variable needs to be expanded beyond one time

Currently - every session is subject to the same timeout value. We would like to request that there be three separate values - one for analysts using Core or Nano, one for customers using the Self-Service Portal and one for API sessions. The three value could be the same or they could be different - giving additional control over the system to administrators.

In addition - we'd like to request that there be a way these values could be set from Core by the administrators. This value currently cannot be set by cloud customers since we do not have access to the servers.

And finally - we would like to see a method for excluding specific accounts from the timeout process - or of at least setting an individual override value. We do this currently (and I know other customers do) by updating the values in IN_SESSION_INFO in scheduled tasks. It would be a big improvement if this was part of the timeout process within the system and would not have to be updated outside of the system.

  • Jim Weaver
  • Oct 26 2021
  • Reviewed by Alemba Product Manager
  • Attach files