Secure Global Desktop 4.40 Administration Guide > Users and Authentication > Login Scripts Supplied With SGD

Login Scripts Supplied With SGD

All login scripts supplied with SGD are stored in the /opt/tarantella/var/serverresources/expect directory. Each script is fully commented.

The login scripts can be divided into the scripts that can be used when configuring applications and the scripts that contain common code.

Login Scripts Used When Configuring Applications

You configure a particular login script for an application as follows:

In the SGD Administration Console, use the Login Script script attribute on the Launch tab for the application.
On the command line, use the --login script command option with the tarantella object commands.

The following table lists the login scripts supplied with SGD that you can set as the Login Script attribute and a description of what they are used for.

Script Name	Description
`unix.exp`	The standard login script for character and X applications. If the Login Script attribute is blank, this script is used by default. Can be used with all Connection Methods.
`securid.exp`	Replacement for `unix.exp` if you are using SecurID for application server authentication.
`windows.exp`	The standard login script for Windows applications If the Login Script attribute is blank, this script is used by default. Calls other login scripts depending on the Windows Protocol attribute.
`3270.exp`	The standard login script for 3270 applications. If the Login Script attribute is blank, this script is used by default. Can be used with all Connection Methods. The script builds a command to run the TeemTalk for UNIX terminal emulation software.
`5250.exp`	The standard login script for 5250 applications. If the Login Script attribute is blank, this script is used by default. Can be used with all Connection Methods. The script builds a command to run the TeemTalk for UNIX terminal emulation software.
`vms.exp`	Used for X or character applications running on VMS application servers. Can be used for all Connection Methods except `rexec`.
`vmsrexec.exp`	Used for X or character applications running on VMS application servers. Can only be used if the Connection Method is `rexec`.
`unixclass.exp`	Script used to create a shadowable UNIX session, for use in a virtual classroom situation.
`winclass.exp`	Script used to create a shadowable Windows session, for use in a virtual classroom situation.
`pupil.exp`	Script used by the pupils when shadowing a teacher in a virtual classroom situation.

Login Scripts Containing Common Code

The following table lists the login scripts supplied with SGD that contain common code and a description of what they are used for. These scripts must not be set as the Login Script attribute for an application.

Script Name	Description
`runsubscript.exp`	The standard wrapper login script used to call all the other SGD login scripts. Sets the environment variables the login scripts are allowed to use.
`procs.exp`	Called by other scripts. Defines common procedures.
`vars.exp`	Called by other scripts. Defines the variables, messages, and timeouts used by the other login scripts.
`securid-vars.exp`	Called by `securid.exp`. Defines additional variables and messages needed for SecurID authentication.
`xauth.exp`	Called by `procs.exp` and `classroom.exp`. Used to handle the X authorization process, including the X authorization permissions for shadowing.
`classroom.exp`	Called by `unixclass.exp`, `winclass.exp`, and `pupil.exp`. Defines common procedures for retrieving the X display to shadow.
`unixwin.exp`	Called by `windows.exp` for Windows applications configured to use the SCO Merge or Citrix ICA Windows Protocol. This script assumes that the user's `PATH` includes the directory in which the Merge or ICA UNIX client software is installed. Although the SCO Merge protocol is no longer supported, legacy windows application objects can continue to use it.
`wcpwts.exp`	Called by `windows.exp` for Windows applications configured to use the Microsoft RDP Windows Protocol.
`wincenter.exp`	Called by `windows.exp` for Windows applications configured to use the WinCenter or Citrix UNIX Integration Services Windows Protocol. Although the WinCenter and Citrix UNIX Integration Services protocols are no longer supported, legacy windows application objects can continue to use them.

Related Topics
Login Script Error Messages Increasing the Launch Timeouts in the Login Scripts Login Script Tcl Commands and Procedures Login Script Variables An Application Does Not Start