| |
A script is a simple piece of text that is stored by the SecureLogin script broker. Each script has a name, called the platform name, which uniquely identifies it within a particular single sign-on database.
In addition, each script has a type, known as the platform type. The platform type specifies the type of application the script refers to and hence which of the SecureLogin components executes it.
SecureLogin scripts execute sequentially from the first line. There are no flow control mechanisms as such. There are, however, instances where a component may choose not to execute certain statements, as in the Dialog/EndDialog statement. Each line in the script consists of one or more arguments.
Arguments are separated by white space (spaces and tabs), unless they are enclosed with quotation marks. For example, the following line contains three arguments:
A simple "command to get started"
After a script has been broken into arguments, the quotation marks are removed. If you need to specify an actual quotation mark in a script, precede it with a \ (for example \").
The first argument on a line is the command. It specifies the action the line takes. (See SecureLogin Commands.) The rest of the arguments on the line, if any, are passed to that command. Different commands take varying numbers of arguments.
If a line begins with a # character, the line is treated as a comment and is ignored in the script language. The following example illustrates this character.
Window "login"
Delay 30
# this delay is so the window is
# created correctly
Type "$Username"
Scripts are interpreted as SecureLogin components perform the sign-in process. This functionality ensures that any variables that are substituted or passtickets that are generated are current.
| |