Publication: SecureTransport 5.3.0 Developer Guide

The environment variables are divided into groups. The following topics describe the predefined environment variables that are passed to agents:

Publication: SecureTransport 5.3.0 Developer Guide

The following environment variables are present in client- and server-initiated sessions. Unless indicated otherwise, each predefined variable is supported by all SecureTransport protocol servers (AS2D, FTPD, HTTPD, PESITD, and SSHD).

Publication: SecureTransport 5.3.0 Developer Guide

SecureTransport offers many predefined environment variables that can be used when creating a condition for a rule. You can also add your own environment variables.

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs as the result of a client request to create a contact in the address book associated with their account.

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs as the result of a client request to delete an existing contact in the address book associated with their account.

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs as the result of a client request to retrieve contacts from the address book associated with their account.

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs as the result of a client request to create a contact in the address book associated with their account.

Publication: SecureTransport 5.3.0 Developer Guide

The following events are used to manage address book contacts:

Publication: SecureTransport 5.3.0 Developer Guide

This event is sent when a file associated with application arrives anywhere inside the subscription folder. If a PGP data transformation was configured for the subscription, the file is a result of the data transformation. PGP data transformations are applied...

Publication: SecureTransport 5.3.0 Developer Guide

This event indicates that a subscription to an application needs to be initialized. The application agent creates the necessary folder hierarchy under subscription folder or performs other initialization tasks. For example, an application creates a readme file in the subscription...

Publication: SecureTransport 5.3.0 Developer Guide

This event indicates an application action needs to be performed according to a schedule associated with the application. The TransferLogMaintence application type uses this event. For information on using schedules to transfer data, see Schedule event.

Publication: SecureTransport 5.3.0 Developer Guide

The following events are part of the application framework and are used to control applications.

Publication: SecureTransport 5.3.0 Developer Guide

The following events are used when starting, authenticating, or stopping a session. The events are listed in the order called for logging in and authenticating a user.

Publication: SecureTransport 5.3.0 Developer Guide

The purpose of the certificate event is to authenticate an end user based on the user's certificate or key. The certificate event is sent to verify the user certificate during SSL negotiation or to verify the user SSH key during...

Publication: SecureTransport 5.3.0 Developer Guide

The CHMOD event occurs in response to a request to change the modes and permissions of a file.

Publication: SecureTransport 5.3.0 Developer Guide

The CWD event occurs in response to a request to change directory. An agent triggered by this event validates the target directory and stores its value. The value is retrieved through the FTP Cmd - PWD event. See FTP Cmd...

Publication: SecureTransport 5.3.0 Developer Guide

Subject to the delete restrictions, the DELE event occurs in response to a request to delete a file.

Publication: SecureTransport 5.3.0 Developer Guide

The directory list event occurs as a result of the directory list command (ls). An agent triggered by this event should send an ls -al-type directory listing to the output stream. The agent can also provide HTML output if the...

Publication: SecureTransport 5.3.0 Developer Guide

The modification time event occurs when a request to get the modification time of a file is made. An agent triggered by this event outputs the modification time to the output stream. The format you use depends on the server...

Publication: SecureTransport 5.3.0 Developer Guide

The MIRR event occurs in response to a request to get a list of mirror locations. An agent triggered by this event outputs mirroring data in the form of a URL, including the pathname in the URL, hostname, and port...