Publication: SecureTransport 5.3.0 Developer Guide

All Transaction Manager events happen within a session. When a session is first created a unique identifier available through the DXAGENT_SESSIONID environment variable is assigned. Agents can associate data with the session using the Session State API. For more information,

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

This event provides user information such as a password, upload restrictions, and access control rights for SecureTransport . The event occurs during the early stages of user login. The output from the configuration agent can contain one or more of

Publication: SecureTransport 5.3.0 Developer Guide

This event follows the user configuration event if a user is authenticated using a password. If the user is authenticated using only a certificate or SSH key, the password authentication event is not sent. Note The password might be verified

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs in the last stages of the login after successful authentication. An agent triggered by this event can set the user cookie and return a login message back to the client. The following topics provide detailed information about

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs when the user session is terminated. An agent triggered by this event can generate a logout message. The following topics provide detailed information about the Logout event: Output stream Exit codes Customization considerations Related topics: Sessions Certificate

Publication: SecureTransport 5.3.0 Developer Guide

File Transfer Authorization events start an upload or download. File Transfer Audit events perform tracking tasks on uploads and downloads. Incoming and outgoing events are used for the following reasons when users upload and download files from a server: To

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs at the start of an upload. Allow or deny permissions for users to upload a file to the server can be defined by the agent triggered by this event. A nonzero exit code prevents uploading. The following

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs at the end of an upload session. It primarily alerts someone that files have been uploaded to the server. The following topics provide detailed information about the Incoming End event: Environment variables Exit codes Customization Considerations Related

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs when an unexpected interruption occurs when a file is being uploaded to the server. This kind of error usually occurs due to network problems. For HTTPS transfers, aborts also generate this event. The following topics provide detailed

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs when the user interrupts a file transmission by using a kill method such as Ctrl+C or break. Depending on the protocol, it can be difficult to distinguish between an error and an abort case. Both HTTPS and

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs at the start of a download. An agent triggered by this event can give or deny permissions for users to download a file. A non-zero return code prevents the download. The following topics provide detailed information about

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs at the end of a download session. An agent triggered by this event primarily alerts you that files have been downloaded from the server. The following topics provide detailed information about the Outgoing End event: Environment variables

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs when an unexpected interruption occurs during a file download from the server. The most common reason for this type of error is usually due to a network problem. For HTTP/S transfers, aborts are handled by this agent.

Publication: SecureTransport 5.3.0 Developer Guide

This event occurs when users interrupts a file transmission using a kill method like Ctrl+C or break. For HTTPS transfers it is not possible to detect an abort. So, aborts are handled by the Outgoing Error Agent. The following topics

Publication: SecureTransport 5.3.0 Developer Guide

These events are used by multiple protocols to move files to or from the server. Every FTP, SSH, or HTTP command that involves file system access has an associated command event. Rules and agents contained in the built-in Streaming rules

Publication: SecureTransport 5.3.0 Developer Guide

The file upload event occurs when a file is in the process of being uploaded. An agent should read the file content data from the input stream. The following topics provide detailed information about the FTP Cmd - STOR event:

Publication: SecureTransport 5.3.0 Developer Guide

The file download event occurs when a file is in the process of being downloaded. An agent triggered by this event should write the file content data to the output stream. The following topics provide detailed information about the FTP

Publication: SecureTransport 5.3.0 Developer Guide

The transfer restart event occurs when restarting a previous upload or download transfer. An agent triggered by this event stores the position in a session state variable ( REST ). When a file download or upload request is received, 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