Knowledgebase: WinGate 6
Authentication - Changing Session Time-out Period when Client Logs Off
Posted by Adrien de Croy (Import) on 24 January 2007 08:04 PM

Applies to version 6.1 and later


In version 6.1 we added the ability to control the length of time that a user session stays active in WinGate. Previously an authenticated user session would drop to an assumed state for 30 seconds when the last application session closed, allowing the user to continue browsing (open a new application session) without the need to reauthenticate. After this time the session would drop and the client would no longer have access through WinGate without reauthenticating.

By editing the WinGate registry file you can change the amount of time that the user session stays active in WinGate.
  • On the WinGate server open the regsitry editor
  • Find the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Settings
  • Right click and add a new DWord Value as follows:
    Value Name: MachineTimeout
    Value Data: 30 (or appropriate setting - this is the time in seconds that a session will stay connected after the user logs off)
  • Right click and add a second DWord Value as follows:
    Value Name: MachineTimeoutAuthAction
    Value Data: (choose the appropriate value as described below)

    0 = leave user assumed for the MachineTimeout period after they log off.
    1 = leave user authenticated for the MachineTimeout period after they log off.
    2 = leave user as guest for the MachineTimeout period after they log off.


You will need to restart the WinGate engine after making these changes.

session time out

If you have any questions about this article please contact Qbik Support.
(1273 vote(s))
Helpful
Not helpful

Comments (0)