Is it possible to set Sessions Timeout?

[NickyDJ]

I'm using WinGate 6.0.3 with Java authenticathion for WWW Proxy Server and it works properly, but i found the users log on to WinGate server and stay connected even if they don't use any service.... in this way their seconds online keep on increasing and they keep busy users license...
I'd like to set a timeout for WinGate Sessions for all the clients... for example, when a client is connected (with Java autenthication) but is idle, it is automatically disconnected (terminate the session) after 5 minutes...
Is it possible with WinGate 6.0.3? Now I'm using "terminate all sessions" in the Scheduler but it is fixed at an established time.... it's not ideal for my purpose...

Many thanks
Nicola

[kgoodknecht]

I'm using WinGate 6.0.3 with Java authenticathion for WWW Proxy Server and it works properly, but i found the users log on to WinGate server and stay connected even if they don't use any service.... in this way their seconds online keep on increasing and they keep busy users license...
I'd like to set a timeout for WinGate Sessions for all the clients... for example, when a client is connected (with Java autenthication) but is idle, it is automatically disconnected (terminate the session) after 5 minutes...
Is it possible with WinGate 6.0.3? Now I'm using "terminate all sessions" in the Scheduler but it is fixed at an established time.... it's not ideal for my purpose...

Many thanks
Nicola

You can set session timeout on all Wingate services, click on the service properties in Gatekeeper then select the sessions tab. Most if not all services have a default session timeout from 60 - 600 seconds adjust the setting to suit your needs. Instant Messeging clients are your biggest problem for keeping services tied up, you can disallow these clients from using the Wingate client. Most IM clients will try to find a protocol to use so you may just tell your users not to use IM clients.

[NickyDJ]

Thanks for your reply...
I already knew the services timout... but this kind of timeout does not terminate the JAVA authentication "session", but the service under the Java authentication only. I need to terminate (close) the Java session because it causes the online seconds to increase and the user license to be "busy"...
The only way I found to close the Java sessions is into the scheduler, as "Terminate all sessions", but this kind of function is indipendent from the possible "idle" status of a session and could close an "active" session at the time you set into the scheduler...
Please let me know...
Nicola

[adrien]

You might be better off using another form of authentication then, such as Basic or NTLM, since these use the WWW service for authentication, rather than the Remote Control Service.

Also then the session and license is only in use whilst the browser is connected, whereas with the java client, the connection is permanent.

However, it shouldn't be using a license count - Remote Control Sessions don't use a license count in WinGate 6.

Adrien