Secure Global Desktop 4.31 Administration Guide > Arrays, servers and load balancing > Managing unauthenticated connections to Secure Global Desktop

Managing unauthenticated connections to Secure Global Desktop

Unauthenticated connections to Secure Global Desktop consume server resources. To prevent this happening, Secure Global Desktop uses timeouts.

For the browser-based webtop, the Secure Global Desktop server applies the timeout and breaks the connection. This causes the Sun Secure Global Desktop Client to exit. Two controls are used:

• an unauthenticated session timeout which controls how long unauthenticated webtop sessions last before they are expired. This is an this is an array-wide property. The default is 600 seconds. You can change this by running:
  tarantella config edit \
--tarantella-config-array-unauthenticatedsessiontimeout seconds
• an unauthenticated session limit which controls the number of unauthenticated webtop sessions a Secure Global Desktop Server can have. This is a server-specific property. The default is 100 sessions. You can change this by running:
  tarantella config edit \
--tarantella-config-server-maxunauthenticatedsessions sessions

For the classic webtop, the Java™ technology client applies the timeout and breaks the connection. This timeout occurs after six AsadKeepAlive packets have been sent by the client. By default, AsadKeepAlive packets are sent every 100 seconds. The interval is configured in the /opt/tarantella/var/docroot/resources/login/sco/tta/boot/strap.html file.

Copyright © 1997-2007 Sun Microsystems, Inc. All rights reserved.