Preventing login time out in client applications
Contents
LoginTimeOut and CheckLoginTimer are part of the Serverconfig and define auto-logout of an idle client login.
Note: since the version 2.2, the CheckLoginTimer is removed, and the value of the AlivePeriod parameter is used instead.
The number of seconds of inactivity before a idle login is forced to logout. The seconds are counted from the last 'heart beat' of the login. Note that this timeout value is valid only for the client logins (that is, the SOAP clients: Cmd4, Ted4, etc...). The Web logins (browsers) are limited to the IIS session timeout value. Default: 1200 = 20 minutes. Minimum active value: 60 = 1 minute. 0 means: no timeout. |
In version 2.2 or newer Not available anymore in the version 2.2 or newer: the time interval of the AlivePeriod is used instead In versions prior to 2.2 The number of seconds between successive Client login timeout verifications.Note that the server timer checks only the timeout of the client logins (that is, the SOAP clients: Cmd4, Ted4, etc...). Default: 300 = 5 minutes. Minimum active value: 60 = 1 minute. 0 means: no checking the login timeout at all. |
Note
The above parameters regard only client applications, and not GN4 Web interface, GNPortal or Tark4. So you don't need to configure them if you don't use Ted4, Fred4, EdAdmin4, Admin etc.
See also
Preventing browser session timeout
Preventing interactive workflow timeout