OFTPClient Component
Properties Methods Events Config Settings Errors
The OFTPClient component implements the Odette File Transfer Protocol.
Syntax
TibeOFTPClient
Remarks
The OFTPClient component may be used to send and receive OFTP files to and from an OFTP server.
Receiving Files
The OFTPClient ReceiveFiles function requires certain server properties be set. You must set the RemoteHost property to the remote location of the desired OFTP server. You may also set a RemotePort if the server is not set to the default protocol port. For client authorization, you must set the ClientSSIDCode, ClientSFIDCode, and ClientPassword properties. And, for server authentication, you must set the ServerSSIDCode, ServerSFIDCode, and ServerPassword properties.
The component will connect to the OFTP server and download all files in the server's outgoing queue, and write these files to the directory specified by DownloadDirectory. The component creates a default location on the local machine based on the values of the DownloadDirectory and the Virtual Filename as received from the server. If a different location is preferred, you may set the LocalFile parameter of the StartTransfer event.
Sending Files
The OFTPClient SendFile function requires the same server and authentication properties to be set as the ReceiveFiles function.
The component will connect to the OFTP server and upload the file contained by the LocalFile parameter. It uses the name specified by VirtualFileName when sending to the server. If this is not specified, the filename of the local file is parsed and used as the virtual filename.
Property List
The following is the full list of the properties of the component with short descriptions. Click on the links for further details.
Certificate | The current selected certificate. |
ClientPassword | The client's password. |
ClientSFIDCode | Client's SFID code. |
ClientSSIDCode | The client's SSID code. |
Compress | Whether or not to compress the outgoing file. |
Connected | Shows whether the component is connected. |
DownloadDirectory | Download directory. |
EncryptionAlgorithm | The encryption algorithm. |
Firewall | A set of properties related to firewall access. |
LocalHost | The name of the local host or user-assigned IP interface through which connections are initiated or accepted. |
MaxRecordSize | The maximum length of a given record. |
Overwrite | Whether or not the component should overwrite files during transfer. |
RecipientCert | The recipient certificate of the message. |
RemoteHost | The domain name or IP address of the OFTP server. |
RemotePort | The port for the OFTP service (default is 3305). |
SecureAuthentication | Whether or not the component should perform secure Odette authentication. |
ServerPassword | The server's password. |
ServerSFIDCode | Server's SFID code. |
ServerSSIDCode | The server's SSID code. |
SignedReceipt | Whether or not to require signed receipts. |
SSLAcceptServerCert | Instructs the component to unconditionally accept the server certificate that matches the supplied certificate. |
SSLCert | The certificate to be used during Secure Sockets Layer (SSL) negotiation. |
Timeout | This property includes the timeout for the component. |
TrustedCerts | A collection of trusted CA certificates. |
UseSSL | Use SSL to access the RemoteHost . |
Version | Which version of the OFTP protocol the component is using. |
VirtualFileDate | The date/time stamp for the virtual file. |
VirtualFileFormat | The structure of the outgoing file. |
VirtualFileSecurityLevel | The level of security for the file. |
Method List
The following is the full list of the methods of the component with short descriptions. Click on the links for further details.
ChangeDirection | Sends a Change Direction (CD) command. |
Config | Sets or retrieves a configuration setting. |
Connect | This method connects to the FTP server without logging in. |
Disconnect | This method disconnects from the server without first logging off. |
DoEvents | This method processes events from the internal message queue. |
ExchangeCertificate | Exchange a certificate with the remote host. |
ImportTrustedCerts | Imports a list of trusted CA certificates. |
Interrupt | This method interrupts the current action. |
Logoff | Logoff from the OFTP server. |
Logon | Logon to the OFTP RemoteHost using the current client credentials. |
ReceiveFiles | Receive any files queued to be sent from the server. |
Reset | Resets the state of the control. |
SendEndResponse | Sends an EERP/NERP asynchronously. |
SendFile | Send the specified file to the server. |
ValidateCert | Validates the certificate with private key. |
ValidateRecipientCert | Validates the recipient certificate. |
Event List
The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.
AcceptFile | Fired when the client receives a file. |
CertificateReceived | Fired when a certificate is received from the remote host. |
EndResponse | Fired every time an end response is received from the server. |
EndTransfer | Fired when a file finishes transferring. |
Error | Fired when information is available about errors during data delivery. |
Log | Fires once for each log message. |
PITrail | Fired when any protocol level communication occurs. |
SSLServerAuthentication | Fired after the server presents its certificate to the client. |
SSLStatus | Fired when secure connection progress messages are available. |
StartTransfer | Fired when a document starts transferring. |
Transfer | Fired while a document transfers (delivers document). |
Config Settings
The following is a list of config settings for the component with short descriptions. Click on the links for further details.
AcceptAnySFIDCode | Indicates that all SFID codes are acceptable. |
AllowRetry | Whether to send a retry indicator when rejecting a file. |
CertificateType | Specifies the type of certificate being supplied. |
ConnectionType | Specifies the type of connection that will be created. |
CreditCount | Specifies the credit value. |
DeleteOnError | Whether received files are deleted when there is an error during processing. |
DisconnectAfterEndSession | Determines if the connection is closed immediately after ending the session. |
EnforceProtocolVersion | Requires the server to support the same OFTP version. |
ExchangeBufferSize | Specifies the data exchange buffer size in bytes. |
ExchangeCertStoreType | Specifies the store type when loading a certificate to be exchanged. |
ExchangeCertSubject | The subject of the certificate being exchanged. |
FailOnUntrustedCert | Whether or not to throw an exception when untrusted certificates are used. |
FileDescription | Additional description information sent with the file. |
FileHashAlgorithm | The hash algorithm to use when sending a file. |
FireEndResponseOnSend | Determines if the EndResponse event is fired for outgoing EERP and NERPs. |
FollowRedirects | Determines behavior when importing trusted certificates and a HTTP redirect is returned. |
FriendlyLogFormat | Determines if a more friendly format is applied to PITrail event out. |
LogLevel | The level of information to log. |
MaskSensitiveData | Masks passwords in logs. |
ReceiptHashAlgorithm | The receipt hash algorithm to request when sending a file. |
ReceivedFileDateTime | The datetime of the file being received. |
ReceivedFileDescription | Additional description information received with the file. |
ReceivedFileEncryptionAlg | The encryption algorithm used for the file being received. |
ReceivedFileName | Returns the name of the received file. |
ReceivedFileNameFormat | The name format of received files. |
ReceivedFileNameFormat | The name format of received files. |
RecipientCertificateType | Specifies the type of recipient certificate being supplied. |
Retry | Indicates whether the recipient allows the send to be retried. |
SendCDAfterEFPA | Specifies whether a CD is always sent after receiving an EFPA. |
TempPath | The path of a directory where temporary files will be created. |
TrustedCertsData | Specifies the source to be used when importing trusted certificates. |
VirtualFileDateFormat | The DateTime format of received files. |
BuildInfo | Information about the product's build. |
CodePage | The system code page used for Unicode to Multibyte translations. |
LicenseInfo | Information about the current license. |
MaskSensitiveData | Whether sensitive data is masked in log messages. |
UseFIPSCompliantAPI | Tells the component whether or not to use FIPS certified APIs. |
UseInternalSecurityAPI | Whether or not to use the system security libraries or an internal implementation. |
Certificate Property (OFTPClient Component)
The current selected certificate.
Syntax
property Certificate: TibeCertificate read get_Certificate write set_Certificate;
Remarks
This property is populated when a specified certificate is found or loaded by the component. Certificate is used for specifying private keys. Set this property to a valid Certificate object to perform different operations such as session authentication, signing a file or receipt, or decryption. To set a certificate, you may set the Encoded field to the encoded certificate. To select a certificate, use the Store and Subject fields.
Please refer to the Certificate type for a complete list of fields.ClientPassword Property (OFTPClient Component)
The client's password.
Syntax
property ClientPassword: String read get_ClientPassword write set_ClientPassword;
Default Value
''
Remarks
The password assigned to the client in the bilateral agreement. This property must be a string of no more than 8 characters long.
ClientSFIDCode Property (OFTPClient Component)
Client's SFID code.
Syntax
property ClientSFIDCode: String read get_ClientSFIDCode write set_ClientSFIDCode;
Default Value
''
Remarks
The SFID code identifies the origin or destination party that is sending or receiving a file, while the SSID code identifies the party that a session is established with. If the SFID and SSID codes do not match, then the party the session is established with is acting as an intermediary, and the party identified by the SFID code is either the origin or final destination.
When acting as an intermediary the component will not perform any security services (i.e. sign, verify, encrypt, decrypt). Security services are to be performed by the origin or destination only. Data should simply be passed along by an intermediary.
ClientSSIDCode Property (OFTPClient Component)
The client's SSID code.
Syntax
property ClientSSIDCode: String read get_ClientSSIDCode write set_ClientSSIDCode;
Default Value
''
Remarks
The identification code of the client. This code may be less than, but no more than 25 characters long. Generally, SSID codes have the following format as specified in RFC 2204 that is based on ISO 6523:
Code Identifier | 'O' - Indicates ODETTE assigned the Organization Identifier. Other
values can be used for non-ODETTE codes.
NOTE: This field is a fixed length of 1 character. |
International Code | A code forming part of the Organization Identifier.
NOTE: This field may be of variable length up to 4 characters long. |
Organization Code | A code forming part of the Organization Identifier. This field may
contain the letters A to Z, the digits 0 to 9, and space and hyphen
characters.
NOTE: This field may be of variable length up to 14 characters long. |
Computer Sub-Address | A locally assigned address which uniquely identifies a system within
an organization (defined by an Organization Identifier).
NOTE: This field may be of variable length up to 6 characters long. |
Compress Property (OFTPClient Component)
Whether or not to compress the outgoing file.
Syntax
property Compress: Boolean read get_Compress write set_Compress;
Default Value
false
Remarks
When sending a file to the trading partner, set this to true for the component to compress the file before sending. The file will first be compressed to a temporary file before being sent.
Note that this is only applicable when Version 2.0 of the protocol is used as indicated by Version.
This property is not available at design time.
Connected Property (OFTPClient Component)
Shows whether the component is connected.
Syntax
property Connected: Boolean read get_Connected;
Default Value
false
Remarks
Use this property to determine whether the component is connected to the remote host or not.
Use the Connect and Disconnect methods to manage the connection.
This property is read-only and not available at design time.
DownloadDirectory Property (OFTPClient Component)
Download directory.
Syntax
property DownloadDirectory: String read get_DownloadDirectory write set_DownloadDirectory;
Default Value
'./'
Remarks
This property contains the location on disk of the folder the component will write received files to. The default for this property is "./", which is the current working directory.
Note: If this property is set to empty string data will not be written to disk and instead will be available through the Transfer event.
EncryptionAlgorithm Property (OFTPClient Component)
The encryption algorithm.
Syntax
property EncryptionAlgorithm: TibeOftpclientEncryptionAlgorithms read get_EncryptionAlgorithm write set_EncryptionAlgorithm;
TibeOftpclientEncryptionAlgorithms = ( encra3DES, encraAES );
Default Value
encra3DES
Remarks
In order to use encryption, you must set the VirtualFileSecurityLevel property. The supported algorithms for encryption are:
3DES (0) | Triple Data Encryption Standard. |
AES (1) | Advanced Encryption Standard with key length of 128. |
This property is not available at design time.
Firewall Property (OFTPClient Component)
A set of properties related to firewall access.
Syntax
property Firewall: TibeFirewall read get_Firewall write set_Firewall;
Remarks
This is a Firewall-type property, which contains fields describing the firewall through which the component will attempt to connect.
Please refer to the Firewall type for a complete list of fields.LocalHost Property (OFTPClient Component)
The name of the local host or user-assigned IP interface through which connections are initiated or accepted.
Syntax
property LocalHost: String read get_LocalHost write set_LocalHost;
Default Value
''
Remarks
This property contains the name of the local host as obtained by the gethostname() system call, or if the user has assigned an IP address, the value of that address.
In multihomed hosts (machines with more than one IP interface) setting LocalHost to the IP address of an interface will make the component initiate connections (or accept in the case of server components) only through that interface. It is recommended to provide an IP address rather than a hostname when setting this property to ensure the desired interface is used.
If the component is connected, the LocalHost property shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multihomed hosts (machines with more than one IP interface).
Note: LocalHost is not persistent. You must always set it in code, and never in the property window.
MaxRecordSize Property (OFTPClient Component)
The maximum length of a given record.
Syntax
property MaxRecordSize: Integer read get_MaxRecordSize write set_MaxRecordSize;
Default Value
0
Remarks
This value determines the maximum length for a record in the outgoing virtual file. When VirtualFileFormat has been set to ffUnstructured or ffText, this value must be zero. When ffFixed or ffVariable, this must be set to a value greater than 0, containing the maximum line length of the outgoing file.
Overwrite Property (OFTPClient Component)
Whether or not the component should overwrite files during transfer.
Syntax
property Overwrite: Boolean read get_Overwrite write set_Overwrite;
Default Value
false
Remarks
This property is a value indicating whether or not the component should overwrite downloaded files. If Overwrite is false, an error will be thrown whenever the local file exists before a receive operation.
RecipientCert Property (OFTPClient Component)
The recipient certificate of the message.
Syntax
property RecipientCert: TibeCertificate read get_RecipientCert write set_RecipientCert;
Remarks
This property specifies the certificate to use when verifying signed files and receipts as well as encrypting files to be sent. This property must be set when SecureAuthentication has been set to true, sending a file and VirtualFileSecurityLevel has been set to slEncrypted or slEncryptedAndSigned, SignedReceipt has been set to true, or a signed file is being received and the server has not included the certificate in the signature.
The RecipientCert property must be filled out with a valid public key Certificate type object. To set a certificate, you may set the Encoded field to the encoded certificate. To select a certificate, use the Store and Subject fields.
This property is not available at design time.
Please refer to the Certificate type for a complete list of fields.RemoteHost Property (OFTPClient Component)
The domain name or IP address of the OFTP server.
Syntax
property RemoteHost: String read get_RemoteHost write set_RemoteHost;
Default Value
''
Remarks
The RemoteHost property specifies the IP address (IP number in dotted internet format) or Domain Name of the OFTP server. It is set before a connection is attempted and cannot be changed once a connection is in progress.
If the RemoteHost property is set to a Domain Name, a DNS request is initiated and upon successful termination of the request, the RemoteHost property is set to the corresponding address. If the search is not successful, an error is returned.
If the component is configured to use a SOCKS firewall, the value assigned to this property may be preceded with an "*". If this is the case, the host name is passed to the firewall unresolved and the firewall performs the DNS resolution.
RemotePort Property (OFTPClient Component)
The port for the OFTP service (default is 3305).
Syntax
property RemotePort: Integer read get_RemotePort write set_RemotePort;
Default Value
3305
Remarks
A valid port number (a value between 1 and 65535) is required for the connection to take place. The property must be set before a connection is attempted and cannot be changed once a connection is established. Any attempt to change this property while connected will fail with an error.
When UseSSL is set to True this property will be set to 6619.
This property is not available at design time.
SecureAuthentication Property (OFTPClient Component)
Whether or not the component should perform secure Odette authentication.
Syntax
property SecureAuthentication: Boolean read get_SecureAuthentication write set_SecureAuthentication;
Default Value
false
Remarks
If true, the component will perform secure authentication when connecting to the server. The secure authentication consists of encrypting and decrypting data sent to and from the server, and verifying that this occurred successfully. Secure authentication may be performed in plaintext or SSL mode.
Both Certificate and RecipientCert properties must be populated when this property is set to true.
This is only valid for version 2.0 of the protocol.
This property is not available at design time.
ServerPassword Property (OFTPClient Component)
The server's password.
Syntax
property ServerPassword: String read get_ServerPassword write set_ServerPassword;
Default Value
''
Remarks
The password assigned to the server in the bilateral agreement. This property must be a string of no more than 8 characters long.
ServerSFIDCode Property (OFTPClient Component)
Server's SFID code.
Syntax
property ServerSFIDCode: String read get_ServerSFIDCode write set_ServerSFIDCode;
Default Value
''
Remarks
The SFID code identifies the origin or destination party that is sending or receiving a file, while the SSID code identifies the party that a session is established with. If the SFID and SSID codes do not match, then the party the session is established with is acting as an intermediary, and the party identified by the SFID code is either the origin or final destination.
When acting as an intermediary the component will not perform any security services (i.e. sign, verify, encrypt, decrypt). Security services are to be performed by the origin or destination only. Data should simply be passed along by an intermediary.
ServerSSIDCode Property (OFTPClient Component)
The server's SSID code.
Syntax
property ServerSSIDCode: String read get_ServerSSIDCode write set_ServerSSIDCode;
Default Value
''
Remarks
The identification code of the server. This code may be less than, but no more than 25 characters long. Generally, SSID codes have the following format as specified in RFC 2204 that is based on ISO 6523:
Code Identifier | 'O' - Indicates ODETTE assigned the Organization Identifier. Other
values can be used for non-ODETTE codes.
NOTE: This field is a fixed length of 1 character. |
International Code | A code forming part of the Organization Identifier.
NOTE: This field may be of variable length up to 4 characters long. |
Organization Code | A code forming part of the Organization Identifier. This field may
contain the letters A to Z, the digits 0 to 9, and space and hyphen
characters.
NOTE: This field may be of variable length up to 14 characters long. |
Computer Sub-Address | A locally assigned address which uniquely identifies a system within
an organization (defined by an Organization Identifier).
NOTE: This field may be of variable length up to 6 characters long. |
SignedReceipt Property (OFTPClient Component)
Whether or not to require signed receipts.
Syntax
property SignedReceipt: Boolean read get_SignedReceipt write set_SignedReceipt;
Default Value
false
Remarks
When sending a file to a trading partner, set this to true if the file receipt should be signed by the server. When this receipt is received by the component, it will be verified during processing.
NOTE: If the server does not attach the public certificate in the signed message, the server's public key must be specified in the RecipientCert property in order for verification to succeed.
This property is not available at design time.
SSLAcceptServerCert Property (OFTPClient Component)
Instructs the component to unconditionally accept the server certificate that matches the supplied certificate.
Syntax
property SSLAcceptServerCert: TibeCertificate read get_SSLAcceptServerCert write set_SSLAcceptServerCert;
Remarks
If it finds any issues with the certificate presented by the server, the component will normally terminate the connection with an error.
You may override this behavior by supplying a value for SSLAcceptServerCert. If the certificate supplied in SSLAcceptServerCert is the same as the certificate presented by the server, then the server certificate is accepted unconditionally, and the connection will continue normally.
Note: This functionality is provided only for cases in which you otherwise know that you are communicating with the right server. If used improperly, this property may create a security breach. Use it at your own risk.
Please refer to the Certificate type for a complete list of fields.SSLCert Property (OFTPClient Component)
The certificate to be used during Secure Sockets Layer (SSL) negotiation.
Syntax
property SSLCert: TibeCertificate read get_SSLCert write set_SSLCert;
Remarks
This property includes the digital certificate that the component will use during SSL negotiation. Set this property to a valid certificate before starting SSL negotiation. To set a certificate, you may set the Encoded field to the encoded certificate. To select a certificate, use the store and subject fields.
Please refer to the Certificate type for a complete list of fields.Timeout Property (OFTPClient Component)
This property includes the timeout for the component.
Syntax
property Timeout: Integer read get_Timeout write set_Timeout;
Default Value
60
Remarks
If the Timeout property is set to 0, all operations return immediately, potentially failing with a WOULDBLOCK error if data cannot be sent immediately.
If Timeout is set to a positive value, data is sent in a blocking manner and the component will wait for the operation to complete before returning control. The component will handle any potential WOULDBLOCK errors internally and automatically retry the operation for a maximum of Timeout seconds.
The component will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive.
If Timeout expires, and the operation is not yet complete, the component raises an exception.
Note: By default, all timeouts are inactivity timeouts, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.
The default value for the Timeout property is 60 seconds.
TrustedCerts Property (OFTPClient Component)
A collection of trusted CA certificates.
Syntax
property TrustedCerts: TibeCertificateList read get_TrustedCerts write set_TrustedCerts;
Remarks
If this collection is populated the component will validate any certificates that are loaded against the CA certificates specified here.
If this collection is not populated no validation will occur. Certificates are imported into this collection by calling the ImportTrustedCerts method.
See also FailOnUntrustedCert and TrustedCertsData.
This property is not available at design time.
Please refer to the Certificate type for a complete list of fields.UseSSL Property (OFTPClient Component)
Use SSL to access the RemoteHost .
Syntax
property UseSSL: Boolean read get_UseSSL write set_UseSSL;
Default Value
false
Remarks
Use this property to determine whether the component uses SSL to connect with the RemoteHost.
This property is only valid when using version 2.0 of the protocol.
Note: Setting this property to True will set RemotePort to 6619.
This property is not available at design time.
Version Property (OFTPClient Component)
Which version of the OFTP protocol the component is using.
Syntax
property Version: TibeTOFTPVersions read get_Version write set_Version;
TibeTOFTPVersions = ( oftpVer12, oftpVer13, oftpVer14, oftpVer20 );
Default Value
oftpVer20
Remarks
This property specifies which version of the OFTP protocol to use. Possible values are:
0 (oftpVer12) | 1.2 |
1 (oftpVer13) | 1.3 |
2 (oftpVer14) | 1.4 |
3 (oftpVer20 - default) | 2.0 |
Note: Version 2.0 (oftpVer20) of the protocol must be used when using security functions. The following properties are only applicable when using Version 2.0:
VirtualFileDate Property (OFTPClient Component)
The date/time stamp for the virtual file.
Syntax
property VirtualFileDate: String read get_VirtualFileDate write set_VirtualFileDate;
Default Value
''
Remarks
Set this to the date/time stamp for the virtual file before sending. If this is not set when sending a file, the current date/time will be used. This property will accept various date formats, but will return the following format only: "MM/dd/yyyy HH:mm:ss".
Supported date formats:
- ddd, d MMM yy HH:mm:ss zzz
- ddd, d MMM yyyy HH:mm:ss zzz
- d MMM yy HH:mm:ss zzz
- d MMM yyyy HH:mm:ss zzz
- dd-MMM-yyyy HH:mm:ss
- ddd, d MMM yy HH:mm:ss zz
- ddd, d MMM yyyy HH:mm:ss zz
- ddd, d MMM yy HH:mm:ss zzz
- ddd, d MMM yyyy HH:mm:ss zzz
- ddd, d MMM yy HH:mm:ss z
- ddd, d MMM yyyy HH:mm:ss z
- ddd, dd MMM yyyy HH:mm:ss 'GMT'
- dddd, MMMM dd, yyyy h:mm:ss tt
- dddd, MMMM dd yyyy h:mm tt
- yyMMddHHmmssZ
- yyyyMMddHHmmssZ
- yyMMddHHmmsszzzz
- yyyyMMddHHmmsszzzz
- yyyyMMddHHmmssffff
- MM/dd/yyyy HH:mm:ss
VirtualFileFormat Property (OFTPClient Component)
The structure of the outgoing file.
Syntax
property VirtualFileFormat: TibeVirtualFileFormats read get_VirtualFileFormat write set_VirtualFileFormat;
TibeVirtualFileFormats = ( ffUnstructured, ffText, ffFixed, ffVariable );
Default Value
ffUnstructured
Remarks
The following values are valid file formats for outgoing virtual files:
0 (Unstructured - default) | The outgoing file is binary and has not structure. There are no records in this type of file. |
1 (Text) | The outgoing file is a text file that consists of lines containing no more than 2048 characters terminated by CRLF. This type contains no records. |
2 (Fixed) | The outgoing file is in fixed file format, which means all records are of the same length. For fixed files, the component expects the file to be in text format with each line containing the MaxRecordSize characters terminated by a CRLF. |
3 (Variable) | The outgoing file is a variable file format, meaning all records are of variable length and are no longer than MaxRecordSize. When using this format, the component will parse out each record as a line terminated by CRLF. Thus, this type of file must be a text file, and must contain lines with less than MaxRecordSize characters. |
Note: When either VirtualFileSecurityLevel has been set to a value other than slNone or Compress has been set to true, all files become ffUnstructured except ffVariable files.
This property is not available at design time.
VirtualFileSecurityLevel Property (OFTPClient Component)
The level of security for the file.
Syntax
property VirtualFileSecurityLevel: TibeVirtualFileSecurityLevels read get_VirtualFileSecurityLevel write set_VirtualFileSecurityLevel;
TibeVirtualFileSecurityLevels = ( slNone, slEncrypted, slSigned, slEncryptedAndSigned );
Default Value
slNone
Remarks
When sending files, set this value to the level of security for the next virtual file to send. After receiving a file, this will be set to the level of security of the last file received.
When encrypting a file, RecipientCert must be set, and when signing a file, the Certificate must be set.
The file will be processed to a temporary file before being sent.
This is only valid for version 2.0 of the protocol.
This property is not available at design time.
ChangeDirection Method (OFTPClient Component)
Sends a Change Direction (CD) command.
Syntax
procedure ChangeDirection();
Remarks
This method sends a Change Direction (CD) command to the remote host when called. In normal operation this should not be used. This should only be used if a condition arises where you must manually change the speaker when communicating with the remote host.
Config Method (OFTPClient Component)
Sets or retrieves a configuration setting.
Syntax
function Config(ConfigurationString: String): String;
Remarks
Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
Connect Method (OFTPClient Component)
This method connects to the FTP server without logging in.
Syntax
procedure Connect();
Remarks
This method establishes a connection with the RemoteHost but does not log in. In most cases, it is recommended to use the Logon method, which will both establish a connection and log in to the server.
This method may be useful in cases in which it is desirable to separate the connection and logon operations, for instance, confirming that a host is available by first creating the connection.
Disconnect Method (OFTPClient Component)
This method disconnects from the server without first logging off.
Syntax
procedure Disconnect();
Remarks
This method immediately disconnects from the server without first logging off.
In most cases, the Logoff method should be used to log off and disconnect from the server. Call the Disconnect method in cases in which it is desirable to immediately disconnect without first logging off.
DoEvents Method (OFTPClient Component)
This method processes events from the internal message queue.
Syntax
procedure DoEvents();
Remarks
When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.
ExchangeCertificate Method (OFTPClient Component)
Exchange a certificate with the remote host.
Syntax
procedure ExchangeCertificate(CertificateStore: String; CertificateExchangeType: Integer);
Remarks
If the remote host supports the certificate exchange feature of OFTP 2.0 this method may be used to send and/or request certificates.
The CertificateStore parameter specifies the location of the certificate to be exchanged. In most cases this will be the path to a .cer file on disk. If the certificate is in another format or is installed to the Windows certificate store please see ExchangeCertStoreType and ExchangeCertSubject for more information.
The CertificateExchangeType parameter determines the type of request. Possible values are:
0 | Request: The component will send the certificate file specified. The remote host will respond with a certificate of it's own. The response may be in a separate session. |
1 | Replace: The component will send the certificate file specified. No certificate is expected in response. The certificate sent here invalidates any previous certificates the remote host has stored. |
2 | Deliver: The component will send the certificate file specified. This is used to respond to a certificate request. It may also be used to send new additional certificates to the remote host. This will not invalidate previous certificates the remote host has stored. |
ImportTrustedCerts Method (OFTPClient Component)
Imports a list of trusted CA certificates.
Syntax
procedure ImportTrustedCerts();
Remarks
When ImportTrustedCerts is called the component will import the CA certificates from the source specified by TrustedCertsData into the TrustedCerts collection.
The component will then validate the trust of certificates when they are loaded.
If trusted CA certificates are not imported no validation will occur (default).
See also FailOnUntrustedCert.
Interrupt Method (OFTPClient Component)
This method interrupts the current action.
Syntax
procedure Interrupt();
Remarks
This method interrupts the current action. If you use SendFile to upload a file, the component will run synchronously until the upload is completed. This method will allow you to stop the file from uploading without disconnecting from the host.
Logoff Method (OFTPClient Component)
Logoff from the OFTP server.
Syntax
procedure Logoff();
Remarks
Logoff from the OFTP server. If that fails, the connection is terminated by the local host.
Logon Method (OFTPClient Component)
Logon to the OFTP RemoteHost using the current client credentials.
Syntax
procedure Logon();
Remarks
Logon to the OFTP server using the current ClientSSIDCode, ClientSFIDCode, and ClientPassword. The component will also check the corresponding server credentials, ServerSSIDCode, ServerSFIDCode, and ServerPassword.
ReceiveFiles Method (OFTPClient Component)
Receive any files queued to be sent from the server.
Syntax
procedure ReceiveFiles();
Remarks
This method connects to the server, and receives any files the server has in its outgoing queue to this particular partner. The files are downloaded to the directory specified by the DownloadDirectory property.
Reset Method (OFTPClient Component)
Resets the state of the control.
Syntax
procedure Reset();
Remarks
Reset resets the state of the component. All properties will be set to their default values.
SendEndResponse Method (OFTPClient Component)
Sends an EERP/NERP asynchronously.
Syntax
procedure SendEndResponse(VirtualFileName: String; VirtualFileDate: String; Destination: String; Originator: String; Creator: String; ReasonCode: Integer; ReasonText: String; FileHash: String; Signature: String);
Remarks
This method sends an EERP/NERP. By default the component will automatically respond with an EERP/NERP when receiving a file. To respond asynchronously instead this method may be used.
To respond asynchronously first set the SendEndResponse parameter of the EndTransfer event to False. This instructs the component to not send a response automatically. Within the EndTransfer event you must also save the values that are required parameters for this method. This includes FileHash, VirtualFileDate, and VirtualFileName. Note: VirtualFileDateFormat must be set to a format that includes the necessary level of accuracy.
Destination should be set to the SFID of the remote host.
Originator should be set to the SFID of the local system. In the case that the component is being used as part of a gateway process to forward traffic to another OFTP host this may be set to the SFID of that host instead.
Creator should be set to the SFID of the local system.
Signature is only applicable if the application is acting as a routing application. In all other cases this should be set to empty string. In the case where the application is acting as a routing application the end response is being forwarded to another entity for processing. The Signature should be set to the value received in the EndResponse event (if populated).
ReasonCode and ReasonText are used to specify error information. If ReasonCode is set to 0 the component will send an EERP. If ReasonCode is set to any non-zero value the component will send a NERP. Common values are:
ReasonCode | ReasonText |
3 | User Code Not Known |
4 | Invalid Password |
9 | Unspecified Reason |
11 | Invalid FileName |
12 | Invalid Destination |
13 | Invalid Origin |
14 | Invalid Storage Record Format |
15 | Maximum Record Length Not Supported |
16 | File Size Too Big |
20 | Invalid Record Count |
21 | Invalid Byte Count |
22 | Access Method Failure |
23 | Duplicate File |
24 | File Direction Refused |
25 | Cipher Suite Not Supported |
26 | Encrypted File Not Allowed |
27 | Unencrypted File Not Allowed |
28 | Compression Not Allowed |
29 | Signed File Not Allowed |
30 | Unsigned File Not Allowed |
31 | File Signature Not Valid |
32 | File Decompression Failed |
33 | File Decryption Failed |
34 | File Processing Failed |
35 | Not Delivered To Recipient |
36 | Not Acknowledged By Recipient |
50 | Transmission Stopped By The Operator |
90 | File Size Incompatible With Recipient's Protocol Version |
99 | Unspecified Reason |
SendFile Method (OFTPClient Component)
Send the specified file to the server.
Syntax
procedure SendFile(LocalFile: String; VirtualFileName: String);
Remarks
This method connects to the server, and uploads the specified file to the server. The LocalFile parameter contains the path and name of the file to send to the server. The VirtualFileName parameter contains the virtual file name of the file being sent. If this parameter is left as an empty string, the component will use the filename contained in the LocalFile parameter by default.
Note: When SetUploadStream has been called with a valid input stream, the data will be uploaded from there instead of the LocalFile.
ValidateCert Method (OFTPClient Component)
Validates the certificate with private key.
Syntax
function ValidateCert(): Boolean;
Remarks
This method optionally validates the certificate specified by Certificate. It is not required to validate the certificate from a technical perspective, but may be desired to ensure the recipient's certificate is valid and issued by a trusted authority.
Before calling this method call ImportTrustedCerts to load the trusted certification information.
When this method is called the component:
- Validates the certificate has not expired
- Validates the certificate was issued by a CA in the TrustedCerts collection. If the certificate is self-signed this step is skipped.
- Validates the certificate has not been revoked. Note that the revocation check will only make use of the CRL distribution point identified in the certificate's extension. If the certificate does not contain a CRL distribution point extension this step is skipped.
ValidateRecipientCert Method (OFTPClient Component)
Validates the recipient certificate.
Syntax
function ValidateRecipientCert(): Boolean;
Remarks
This method optionally validates the certificate specified by RecipientCert. It is not required to validate the certificate from a technical perspective, but may be desired to ensure the recipient's certificate is valid and issued by a trusted authority.
Before calling this method call ImportTrustedCerts to load the trusted certification information.
When this method is called the component:
- Validates the certificate has not expired
- Validates the certificate was issued by a CA in the TrustedCerts collection. If the certificate is self-signed this step is skipped.
- Validates the certificate has not been revoked. Note that the revocation check will only make use of the CRL distribution point identified in the certificate's extension. If the certificate does not contain a CRL distribution point extension this step is skipped.
AcceptFile Event (OFTPClient Component)
Fired when the client receives a file.
Syntax
type TAcceptFileEvent = procedure ( Sender: TObject; const VirtualFileName: String; const VirtualFileDate: String; const Destination: String; const Originator: String; var Accept: Boolean; var FileName: String; var Overwrite: Boolean; var ErrorCode: Integer; var ErrorDescription: String ) of Object;
property OnAcceptFile: TAcceptFileEvent read FOnAcceptFile write FOnAcceptFile;
Remarks
This event controls the behavior when the client receives a file.
VirtualFileName holds the name of the file being received.
VirtualFileDate holds the date associated with the file in the format specified by VirtualFileDateFormat. The default value is "MM/dd/yyyy HH:mm:ss".
Destination identifies the receiver (SFID) code in the send file request. If the file was intended for this server this will match the value in ServerSFIDCode
Originator identifies the sender (SFID) code in the send file request.
Accept is true by default, and must be set to False in order to reject the file.
Filename will be populated with the full path and filename that will be written. It may be changed within this event to specify a new location. The Filename is determined by combining the path specified in DownloadDirectory and the name received from the client.
Overwrite is false by default, but may be set to true to overwrite existing files on disk.
ErrorCode controls the error returned to the client when Accept is set to False. If this is not set the component will use a value of 99 to indicate a general error.
ErrorDescription may also be set to include an error message. If this is not set the component will automatically include an error message based on the ErrorCode specified. Common error codes and their corresponding error messages are listed below.
ErrorCode | ErrorMessage |
1 | Invalid filename. |
2 | Invalid destination. |
3 | Invalid origin. |
4 | Storage record format not supported. |
5 | Maximum record length not supported. |
6 | File size is too big. |
10 | Invalid record count. |
11 | Invalid byte count. |
12 | Access method failure. |
13 | Duplicate file. |
14 | File direction refused. |
15 | Cipher suite not supported. |
16 | Encrypted file not allowed. |
17 | Unencrypted file not allowed. |
18 | Compression not allowed. |
19 | Signed file not allowed. |
20 | Unsigned file not allowed. |
99 | Unspecified reason. |
CertificateReceived Event (OFTPClient Component)
Fired when a certificate is received from the remote host.
Syntax
type TCertificateReceivedEvent = procedure ( Sender: TObject; const CertificateFileName: String; CertificateExchangeType: Integer ) of Object;
property OnCertificateReceived: TCertificateReceivedEvent read FOnCertificateReceived write FOnCertificateReceived;
Remarks
This event provides information about the certificate file that was sent by the remote host.
When the remote host sends a certificate using the Certificate Exchange feature of OFTP 2.0, this event provides information about it. The certificate file will be written to the DownloadDirectory. After the file is written to DownloadDirectory this event will fire.
The CertificateFilemame parameter holds the filename of the received certificate.
The CertificateExchangeType parameter identifies the type of request associated with the certificate. Possible values are:
0 | Request: The component received a certificate and request from the remote host. Respond using the ExchangeCertificate method using a CertificateExchangeType of 3 (Deliver). The response may be in a separate session. |
1 | Replace: The component received a certificate from the remote host. No response is expected. The certificate received here invalidates any previously stored certificates for this configuration. |
2 | Deliver: The component received a certificate from the remote host. This is either a response to a certificate request, or a new additional certificates from the remote host. This will not invalidate previous certificates stored for this configuration. |
EndResponse Event (OFTPClient Component)
Fired every time an end response is received from the server.
Syntax
type TEndResponseEvent = procedure ( Sender: TObject; const VirtualFileName: String; const VirtualFileDate: String; const Destination: String; const Originator: String; const Creator: String; ReasonCode: Integer; const ReasonText: String; var FileHash: String; const Signature: String; Direction: Integer ) of Object;
property OnEndResponse: TEndResponseEvent read FOnEndResponse write FOnEndResponse;
Remarks
This event contains information received from an either an End-To-End Response or a Negative End Response received from the server.
An End-To-End Response will not contain values for the ReasonCode, ReasonText, or Creator parameters.
VirtualFileName specifies the name of the file.
VirtualFileDate holds the VirtualFileDate value in the format specified by VirtualFileDateFormat. The default value is "MM/dd/yyyy HH:mm:ss".
Destination is the SFID of the destination system (this component).
Originator identifies the system that originated the end response. This is typically the same as Creator and holds the remote system's SFID.
Creator is the SFID of the remote system.
Direction specifies whether the end response is being received or sent. Possible values are:
0 | Received |
1 | Sent |
FileHash is populated if the OFTP Version is 2.0 and a signed receipt was originally requested. FileHash may also be specified with the expected value in the case where an asynchronous EndResponse is received. The expected value may be obtained from the EndTransfer event when initially sending the file.
Signature is only applicable when the OFTP version is 2.0 and the application is acting as a routing application where the end response will be forwarded on to another entity. In this case Signature will be populated if the end response is signed. This should be stored and supplied when forwarding the response with the SendEndResponse method.
ReasonCode and ReasonText identify the error if a Negative End Response (NERP) was received. A value of 0 indicates there was no an error and the response is an End-To-End Response (EERP). Common values are:
ReasonCode | ReasonText |
3 | User Code Not Known |
4 | Invalid Password |
9 | Unspecified Reason |
11 | Invalid FileName |
12 | Invalid Destination |
13 | Invalid Origin |
14 | Invalid Storage Record Format |
15 | Maximum Record Length Not Supported |
16 | File Size Too Big |
20 | Invalid Record Count |
21 | Invalid Byte Count |
22 | Access Method Failure |
23 | Duplicate File |
24 | File Direction Refused |
25 | Cipher Suite Not Supported |
26 | Encrypted File Not Allowed |
27 | Unencrypted File Not Allowed |
28 | Compression Not Allowed |
29 | Signed File Not Allowed |
30 | Unsigned File Not Allowed |
31 | File Signature Not Valid |
32 | File Decompression Failed |
33 | File Decryption Failed |
34 | File Processing Failed |
35 | Not Delivered To Recipient |
36 | Not Acknowledged By Recipient |
50 | Transmission Stopped By The Operator |
90 | File Size Incompatible With Recipient's Protocol Version |
99 | Unspecified Reason |
EndTransfer Event (OFTPClient Component)
Fired when a file finishes transferring.
Syntax
type TEndTransferEvent = procedure ( Sender: TObject; Direction: Integer; const LocalFile: String; const VirtualFileName: String; const VirtualFileDate: String; const Destination: String; const Originator: String; ReasonCode: Integer; const ReasonText: String; FileSize: Int64; const FileHash: String; var SendEndResponse: Boolean ) of Object;
property OnEndTransfer: TEndTransferEvent read FOnEndTransfer write FOnEndTransfer;
Remarks
The EndTransfer event is fired when a file is sent or received by the component.
The FileSize parameter gives the size of the file that was sent or received.
The Direction parameter shows whether the client or the server is sending the data.
0 (Client) | The file originated from the client. |
1 (Server) | The file originated from the server. |
VirtualFileName holds the filename.
VirtualFileDate holds the date associated with the file in the format specified by VirtualFileDateFormat. The default value is "MM/dd/yyyy HH:mm:ss".
Originator identifies the sender (SFID) code in the send file request.
Destination identifies the receiver (SFID) code in the send file request.
SendEndResponse indicates whether the EERP/NERP for this request should be sent synchronously or asynchronously. When this parameter is True (default) the component will automatically respond with an EERP/NERP synchronously. To respond asynchronously set this parameter to False. You may then use the SendEndResponse method to send the response at a later time. See SendEndResponse for more details. Note: VirtualFileDateFormat must be set to a format that includes the necessary level of accuracy.
FileHash holds the hash of the file being transmitted. This is only applicable when the OFTP version is 2.0 and the sender requested a signed receipt. When receiving files this value should be saved if you wish to respond asynchronously using SendEndResponse. See SendEndResponse for more details.
LocalFile holds the full path to the file that will be written.
ReasonCode and ReasonText identify the error if a Negative End Response (NERP) was received. A value of 0 indicates there was no an error and the response is an End-To-End Response (EERP). Common values are:
ReasonCode | ReasonText |
3 | User Code Not Known |
4 | Invalid Password |
9 | Unspecified Reason |
11 | Invalid FileName |
12 | Invalid Destination |
13 | Invalid Origin |
14 | Invalid Storage Record Format |
15 | Maximum Record Length Not Supported |
16 | File Size Too Big |
20 | Invalid Record Count |
21 | Invalid Byte Count |
22 | Access Method Failure |
23 | Duplicate File |
24 | File Direction Refused |
25 | Cipher Suite Not Supported |
26 | Encrypted File Not Allowed |
27 | Unencrypted File Not Allowed |
28 | Compression Not Allowed |
29 | Signed File Not Allowed |
30 | Unsigned File Not Allowed |
31 | File Signature Not Valid |
32 | File Decompression Failed |
33 | File Decryption Failed |
34 | File Processing Failed |
35 | Not Delivered To Recipient |
36 | Not Acknowledged By Recipient |
50 | Transmission Stopped By The Operator |
90 | File Size Incompatible With Recipient's Protocol Version |
99 | Unspecified Reason |
Error Event (OFTPClient Component)
Fired when information is available about errors during data delivery.
Syntax
type TErrorEvent = procedure ( Sender: TObject; ErrorCode: Integer; const Description: String ) of Object;
property OnError: TErrorEvent read FOnError write FOnError;
Remarks
The Error event is fired in case of exceptional conditions during message processing. Normally the component raises an exception.
The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.
Log Event (OFTPClient Component)
Fires once for each log message.
Syntax
type TLogEvent = procedure ( Sender: TObject; LogLevel: Integer; const Message: String; const LogType: String ) of Object;
property OnLog: TLogEvent read FOnLog write FOnLog;
Remarks
This event fires once for each log message generated by the component. The verbosity is controlled by the LogLevel setting.
LogLevel indicates the level of message. Possible values are:
0 (None) | No messages are logged. |
1 (Info - Default) | Informational events such as OFTP commands which are sent and received. |
2 (Verbose) | Detailed data such as individual packet information is logged. |
3 (Debug) | Debug data including all relevant sent and received bytes are logged. |
Message is the log entry.
LogType identifies the type of log entry. Possible values are:
- "Info"
- "OFTP"
PITrail Event (OFTPClient Component)
Fired when any protocol level communication occurs.
Syntax
type TPITrailEvent = procedure ( Sender: TObject; Direction: Integer; const Data: String; const DataB: TBytes; CommandId: Integer; const CommandDescription: String ) of Object;
property OnPITrail: TPITrailEvent read FOnPITrail write FOnPITrail;
Remarks
This event provides information about the protocol level communication between the client and server.
The Direction parameter specifies who sent the command.
0 (Client) | The command originated from the connected client. |
1 (Server) | The command originated from the server. |
The CommandId and CommandDescription parameters specify which command was sent. The table below shows possible values.
CommandId | CommandDescription |
50 | SFPA (Start File Positive Answer) |
51 | SFNA (Start File Negative Answer) |
52 | EFPA (End File Positive Answer) |
53 | EFNA (End File Negative Answer) |
65 | AUCH (Authentication Challenge) |
67 | CDT (Set Credit) |
68 | DATA (Data Exchange Buffer) |
69 | EERP (End to End Response) |
70 | ESID (End Session) |
72 | SFID (Start File) |
73 | SSRM (Start Session Ready Message) |
74 | SECD (Security Change Direction) |
78 | NERP (Negative End Response) |
80 | RTR (Ready To Receive) |
82 | CD (Change Direction) |
83 | AURP (Authentication Response) |
84 | EFID (End File) |
88 | SSID (Start Session) |
The Data parameter contains the raw OFTP packet.
SSLServerAuthentication Event (OFTPClient Component)
Fired after the server presents its certificate to the client.
Syntax
type TSSLServerAuthenticationEvent = procedure ( Sender: TObject; const CertEncoded: String; const CertEncodedB: TBytes; const CertSubject: String; const CertIssuer: String; const Status: String; var Accept: Boolean ) of Object;
property OnSSLServerAuthentication: TSSLServerAuthenticationEvent read FOnSSLServerAuthentication write FOnSSLServerAuthentication;
Remarks
During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.
When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.
SSLStatus Event (OFTPClient Component)
Fired when secure connection progress messages are available.
Syntax
type TSSLStatusEvent = procedure ( Sender: TObject; const Message: String ) of Object;
property OnSSLStatus: TSSLStatusEvent read FOnSSLStatus write FOnSSLStatus;
Remarks
The event is fired for informational and logging purposes only. This event tracks the progress of the connection.
StartTransfer Event (OFTPClient Component)
Fired when a document starts transferring.
Syntax
type TStartTransferEvent = procedure ( Sender: TObject; Direction: Integer; var LocalFile: String; const VirtualFileName: String; const VirtualFileDate: String; const Destination: String; const Originator: String ) of Object;
property OnStartTransfer: TStartTransferEvent read FOnStartTransfer write FOnStartTransfer;
Remarks
This event fires when a file transfer begins.
Direction specifies if the client or server sent the file.
0 (Client) | The file originated from the client. |
1 (Server) | The file originated from the server. |
VirtualFileName holds the filename.
VirtualFileDate holds the date associated with the file in the format "MM/dd/yyyy HH:mm:ss".
Originator identifies the sender (SFID) code in the send file request.
Destination identifies the receiver (SFID) code in the send file request.
LocalFile holds the full path to the file that will be written.
Transfer Event (OFTPClient Component)
Fired while a document transfers (delivers document).
Syntax
type TTransferEvent = procedure ( Sender: TObject; Direction: Integer; const LocalFile: String; const VirtualFileName: String; const VirtualFileDate: String; const Destination: String; const Originator: String; BytesTransferred: Int64; const Text: String; const TextB: TBytes ) of Object;
property OnTransfer: TTransferEvent read FOnTransfer write FOnTransfer;
Remarks
The Text parameter contains the portion of the document text being retrieved. It is empty if data is being posted to the server.
The BytesTransferred parameter contains the number of bytes transferred in this Direction since the beginning of the document text.
The Direction parameter shows whether the client (0) or the server (1) is sending the data.
VirtualFileName holds the filename.
VirtualFileDate holds the date associated with the file in the format specified by VirtualFileDateFormat. The default value is "MM/dd/yyyy HH:mm:ss".
Originator identifies the sender (SFID) code in the send file request.
Destination identifies the receiver (SFID) code in the send file request.
LocalFile holds the full path to the file that will be written.
Certificate Type
This is the digital certificate being used.
Remarks
This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.
Fields
EffectiveDate
String (read-only)
Default Value: ""
The date on which this certificate becomes valid. Before this date, it is not valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date:
23-Jan-2000 15:00:00.
ExpirationDate
String (read-only)
Default Value: ""
The date on which the certificate expires. After this date, the certificate will no longer be valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date:
23-Jan-2001 15:00:00.
ExtendedKeyUsage
String (read-only)
Default Value: ""
A comma-delimited list of extended key usage identifiers. These are the same as ASN.1 object identifiers (OIDs).
Fingerprint
String (read-only)
Default Value: ""
The hex-encoded, 16-byte MD5 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.
The following example illustrates the format: bc:2a:72:af:fe:58:17:43:7a:5f:ba:5a:7c:90:f7:02
FingerprintSHA1
String (read-only)
Default Value: ""
The hex-encoded, 20-byte SHA-1 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.
The following example illustrates the format: 30:7b:fa:38:65:83:ff:da:b4:4e:07:3f:17:b8:a4:ed:80:be:ff:84
FingerprintSHA256
String (read-only)
Default Value: ""
The hex-encoded, 32-byte SHA-256 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.
The following example illustrates the format: 6a:80:5c:33:a9:43:ea:b0:96:12:8a:64:96:30:ef:4a:8a:96:86:ce:f4:c7:be:10:24:8e:2b:60:9e:f3:59:53
Issuer
String (read-only)
Default Value: ""
The issuer of the certificate. This property contains a string representation of the name of the issuing authority for the certificate.
PrivateKey
String (read-only)
Default Value: ""
The private key of the certificate (if available). The key is provided as PEM/Base64-encoded data.
Note: The PrivateKey may be available but not exportable. In this case, PrivateKey returns an empty string.
PrivateKeyAvailable
Boolean (read-only)
Default Value: False
Whether a PrivateKey is available for the selected certificate. If PrivateKeyAvailable is True, the certificate may be used for authentication purposes (e.g., server authentication).
PrivateKeyContainer
String (read-only)
Default Value: ""
The name of the PrivateKey container for the certificate (if available). This functionality is available only on Windows platforms.
PublicKey
String (read-only)
Default Value: ""
The public key of the certificate. The key is provided as PEM/Base64-encoded data.
PublicKeyAlgorithm
String (read-only)
Default Value: ""
The textual description of the certificate's public key algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_DH") or an object identifier (OID) string representing the algorithm.
PublicKeyLength
Integer (read-only)
Default Value: 0
The length of the certificate's public key (in bits). Common values are 512, 1024, and 2048.
SerialNumber
String (read-only)
Default Value: ""
The serial number of the certificate encoded as a string. The number is encoded as a series of hexadecimal digits, with each pair representing a byte of the serial number.
SignatureAlgorithm
String (read-only)
Default Value: ""
The text description of the certificate's signature algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_MD5RSA") or an object identifier (OID) string representing the algorithm.
Store
String
Default Value: "MY"
The name of the certificate store for the client certificate.
The StoreType property denotes the type of the certificate store specified by Store. If the store is password-protected, specify the password in StorePassword.
Store is used in conjunction with the Subject property to specify client certificates. If Store has a value, and Subject or Encoded is set, a search for a certificate is initiated. Please see the Subject property for details.
Designations of certificate stores are platform dependent.
The following designations are the most common User and Machine certificate stores in Windows:
MY | A certificate store holding personal certificates with their associated private keys. |
CA | Certifying authority certificates. |
ROOT | Root certificates. |
When the certificate store type is cstPFXFile, this property must be set to the name of the file. When the type is cstPFXBlob, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).
StoreB
TBytes
Default Value: "MY"
The name of the certificate store for the client certificate.
The StoreType property denotes the type of the certificate store specified by Store. If the store is password-protected, specify the password in StorePassword.
Store is used in conjunction with the Subject property to specify client certificates. If Store has a value, and Subject or Encoded is set, a search for a certificate is initiated. Please see the Subject property for details.
Designations of certificate stores are platform dependent.
The following designations are the most common User and Machine certificate stores in Windows:
MY | A certificate store holding personal certificates with their associated private keys. |
CA | Certifying authority certificates. |
ROOT | Root certificates. |
When the certificate store type is cstPFXFile, this property must be set to the name of the file. When the type is cstPFXBlob, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).
StorePassword
String
Default Value: ""
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
StoreType
TibeCertStoreTypes
Default Value: 0
The type of certificate store for this certificate.
The component supports both public and private keys in a variety of formats. When the cstAuto value is used, the component will automatically determine the type. This property can take one of the following values:
0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user.
Note: This store type is not available in Java. |
1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store.
Note: This store type is not available in Java. |
2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. |
3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. |
4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates.
Note: This store type is only available in Java. |
5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format.
Note: This store type is only available in Java. |
6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. |
8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. |
11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. |
12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. |
13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store).
Note: This store type is only available in Java and .NET. |
22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format.
Note: This store type is only available in Java and .NET. |
23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface.
To use a security key, the necessary data must first be collected using the CertMgr component. The ListStoreCertificates method may be called after setting CertStoreType to cstPKCS11, CertStorePassword to the PIN, and CertStore to the full path of the PKCS#11 DLL. The certificate information returned in the CertList event's CertEncoded parameter may be saved for later use. When using a certificate, pass the previously saved security key information as the Store and set StorePassword to the PIN. Code Example. SSH Authentication with Security Key:
|
99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |
SubjectAltNames
String (read-only)
Default Value: ""
Comma-separated lists of alternative subject names for the certificate.
ThumbprintMD5
String (read-only)
Default Value: ""
The MD5 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.
ThumbprintSHA1
String (read-only)
Default Value: ""
The SHA-1 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.
ThumbprintSHA256
String (read-only)
Default Value: ""
The SHA-256 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.
Usage
String (read-only)
Default Value: ""
The text description of UsageFlags.
This value will be one or more of the following strings and will be separated by commas:
- Digital Signature
- Non-Repudiation
- Key Encipherment
- Data Encipherment
- Key Agreement
- Certificate Signing
- CRL Signing
- Encipher Only
If the provider is OpenSSL, the value is a comma-separated list of X.509 certificate extension names.
UsageFlags
Integer (read-only)
Default Value: 0
The flags that show intended use for the certificate. The value of UsageFlags is a combination of the following flags:
0x80 | Digital Signature |
0x40 | Non-Repudiation |
0x20 | Key Encipherment |
0x10 | Data Encipherment |
0x08 | Key Agreement |
0x04 | Certificate Signing |
0x02 | CRL Signing |
0x01 | Encipher Only |
Please see the Usage property for a text representation of UsageFlags.
This functionality currently is not available when the provider is OpenSSL.
Version
String (read-only)
Default Value: ""
The certificate's version number. The possible values are the strings "V1", "V2", and "V3".
Subject
String
Default Value: ""
The subject of the certificate used for client authentication.
This property must be set after all other certificate properties are set. When this property is set, a search is performed in the current certificate store to locate a certificate with a matching subject.
If a matching certificate is found, the property is set to the full subject of the matching certificate.
If an exact match is not found, the store is searched for subjects containing the value of the property.
If a match is still not found, the property is set to an empty string, and no certificate is selected.
The special value "*" picks a random certificate in the certificate store.
The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=support@nsoftware.com". Common fields and their meanings are as follows:
Field | Meaning |
CN | Common Name. This is commonly a hostname like www.server.com. |
O | Organization |
OU | Organizational Unit |
L | Locality |
S | State |
C | Country |
E | Email Address |
If a field value contains a comma, it must be quoted.
Encoded
String
Default Value: ""
The certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The Store and Subject properties also may be used to specify a certificate.
When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.
EncodedB
TBytes
Default Value: ""
The certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The Store and Subject properties also may be used to specify a certificate.
When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.
Constructors
>
constructor Create();
Creates a instance whose properties can be set. This is useful for use with when generating new certificates.
constructor Create(valEncoded: TBytes);
Parses Encoded as an X.509 public key.
constructor Create(valStoreType: TibeCertStoreTypes; valStore: String; valStorePassword: String; valSubject: String);
StoreType identifies the type of certificate store to use. See for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store.
After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The Subject parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.
constructor Create(valStoreType: TibeCertStoreTypes; valStore: TBytes; valStorePassword: String; valSubject: String);
StoreType identifies the type of certificate store to use. See for descriptions of the different certificate stores. Store is a byte array containing the certificate data. StorePassword is the password used to protect the store.
After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The Subject parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.
Firewall Type
The firewall the component will connect through.
Remarks
When connecting through a firewall, this type is used to specify different properties of the firewall, such as the firewall Host and the FirewallType.
Fields
AutoDetect
Boolean
Default Value: False
Whether to automatically detect and use firewall system settings, if available.
FirewallType
TibeFirewallTypes
Default Value: 0
The type of firewall to connect through. The applicable values are as follows:
fwNone (0) | No firewall (default setting). |
fwTunnel (1) | Connect through a tunneling proxy. Port is set to 80. |
fwSOCKS4 (2) | Connect through a SOCKS4 Proxy. Port is set to 1080. |
fwSOCKS5 (3) | Connect through a SOCKS5 Proxy. Port is set to 1080. |
fwSOCKS4A (10) | Connect through a SOCKS4A Proxy. Port is set to 1080. |
Host
String
Default Value: ""
The name or IP address of the firewall (optional). If a Host is given, the requested connections will be authenticated through the specified firewall when connecting.
If this property is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, this property is set to the corresponding address. If the search is not successful, the component raises an exception.
Password
String
Default Value: ""
A password if authentication is to be used when connecting through the firewall. If Host is specified, the User and Password properties are used to connect and authenticate to the given firewall. If the authentication fails, the component raises an exception.
Port
Integer
Default Value: 0
The Transmission Control Protocol (TCP) port for the firewall Host. See the description of the Host property for details.
Note: This property is set automatically when FirewallType is set to a valid value. See the description of the FirewallType property for details.
User
String
Default Value: ""
A username if authentication is to be used when connecting through a firewall. If Host is specified, this property and the Password property are used to connect and authenticate to the given Firewall. If the authentication fails, the component raises an exception.
Constructors
constructor Create();
Config Settings (OFTPClient Component)
The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.OFTPClient Config Settings
When set to False (default) the component will send a value indicating the server should not retry the send operation.
component.Config("CertificateType=3");
component.Certificate = mySigningCertificate;
Possible values are:
0 (default) | All Operations |
1 | Session Authentication |
2 | Decryption |
3 | Signing |
4 | Receipt Signing |
0 | Both (Default) |
1 | Send Only |
2 | Receive Only |
When this is set to True (default) and there is an error during processing the original unprocessed file will be deleted and no files will be placed in DownloadDirectory.
When set to True, if the server's OFTP version does not match the client's Version, the component raises an exception. When set to False (default), if the server's OFTP version does not match the client's Version, the component will use the lowest mutually supported version.
For a list of possible values please see CertStoreType. Also see ExchangeCertSubject.
0 | sha1 |
1 | sha256 (Default) |
2 | sha512 |
0 (default) | Never follow redirects. An exception will be thrown. |
1 | Always follow redirects. The redirect will be automatically followed. |
2 | Follow same scheme redirects. Follow the redirect if it matches the same scheme (http:// or https://). |
0 (None) | No messages are logged. |
1 (Info - Default) | Informational events such as OFTP commands which are sent and received. |
2 (Verbose) | Detailed data such as individual packet information is logged. |
3 (Debug) | Debug data including all relevant sent and received bytes are logged. |
0 | sha1 (Default) |
1 | sha256 |
2 | sha512 |
0 | 3DES (Triple Data Encryption Standard). |
1 | AES (Advanced Encryption Standard with key length of 128). |
- %VirtualFileName%
- %VirtualFileDate%
- %Originator%
- %Destination%
- %UserData%
- %CurrentTime%
- %GUID%
The '%VirtualFileDate%' macro also supports date formatting through the use of an optional DateTime format string. The format of the macro with the date format string included is:
- %VirtualFileDate:CustomFormat%
- %VirtualFileName%
- %VirtualFileDate%
- %Originator%
- %Destination%
- %UserData%
- %CurrentTime%
- %GUID%
The '%VirtualFileDate%' macro also supports date formatting through the use of an optional DateTime format string. The format of the macro with the date format string included is:
- %VirtualFileDate:CustomFormat%
- %VirtualFileName%
- %VirtualFileDate%
- %Originator%
- %Destination%
- %UserData%
- %CurrentTime%
- %GUID%
The '%VirtualFileDate%' macro also supports date formatting through the use of an optional DateTime format string. The format of the macro with the date format string included is:
- %VirtualFileDate:CustomFormat%
- %VirtualFileName%
- %VirtualFileDate%
- %Originator%
- %Destination%
- %UserData%
- %CurrentTime%
- %GUID%
The '%VirtualFileDate%' macro also supports date formatting through the use of an optional DateTime format string. The format of the macro with the date format string included is:
- %VirtualFileDate:CustomFormat%
component.Config("RecipientCertificateType=3");
component.RecipientCert = mySignatureVerificationCertificate;
Possible values are:
0 (default) | All Operations |
1 | Session Authentication |
2 | Encryption |
3 | Signature Verification |
4 | Receipt Signature Verification |
When set to True, this overrides the default behavior and will always send a CD command regardless of whether the indicator is set in the EFPA.
This should only be set if there is a specific reason to do so. In most cases it is not necessary.
- Compress is true
- VirtualFileSecurityLevel is set to slEncrypted
- VirtualFileSecurityLevel is set to slSigned
- VirtualFileSecurityLevel is set to slEncryptedAndSigned
Note that VirtualFileSecurityLevel is only applicable when Version is set to oftpVer20.
When using OFTP v2.0 If the component is configured to respond to EERP and NERP messages asynchronously this should be set to the value "yyyyMMddHHmmssffff" or a similar format that includes the same level of accuracy. This is required to ensure that when calling SendEndResponse the value saved from within the EndTransfer event has the necessary data when sending a response.
Base Config Settings
The following is a list of valid code page identifiers:
Identifier | Name |
037 | IBM EBCDIC - U.S./Canada |
437 | OEM - United States |
500 | IBM EBCDIC - International |
708 | Arabic - ASMO 708 |
709 | Arabic - ASMO 449+, BCON V4 |
710 | Arabic - Transparent Arabic |
720 | Arabic - Transparent ASMO |
737 | OEM - Greek (formerly 437G) |
775 | OEM - Baltic |
850 | OEM - Multilingual Latin I |
852 | OEM - Latin II |
855 | OEM - Cyrillic (primarily Russian) |
857 | OEM - Turkish |
858 | OEM - Multilingual Latin I + Euro symbol |
860 | OEM - Portuguese |
861 | OEM - Icelandic |
862 | OEM - Hebrew |
863 | OEM - Canadian-French |
864 | OEM - Arabic |
865 | OEM - Nordic |
866 | OEM - Russian |
869 | OEM - Modern Greek |
870 | IBM EBCDIC - Multilingual/ROECE (Latin-2) |
874 | ANSI/OEM - Thai (same as 28605, ISO 8859-15) |
875 | IBM EBCDIC - Modern Greek |
932 | ANSI/OEM - Japanese, Shift-JIS |
936 | ANSI/OEM - Simplified Chinese (PRC, Singapore) |
949 | ANSI/OEM - Korean (Unified Hangul Code) |
950 | ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC) |
1026 | IBM EBCDIC - Turkish (Latin-5) |
1047 | IBM EBCDIC - Latin 1/Open System |
1140 | IBM EBCDIC - U.S./Canada (037 + Euro symbol) |
1141 | IBM EBCDIC - Germany (20273 + Euro symbol) |
1142 | IBM EBCDIC - Denmark/Norway (20277 + Euro symbol) |
1143 | IBM EBCDIC - Finland/Sweden (20278 + Euro symbol) |
1144 | IBM EBCDIC - Italy (20280 + Euro symbol) |
1145 | IBM EBCDIC - Latin America/Spain (20284 + Euro symbol) |
1146 | IBM EBCDIC - United Kingdom (20285 + Euro symbol) |
1147 | IBM EBCDIC - France (20297 + Euro symbol) |
1148 | IBM EBCDIC - International (500 + Euro symbol) |
1149 | IBM EBCDIC - Icelandic (20871 + Euro symbol) |
1200 | Unicode UCS-2 Little-Endian (BMP of ISO 10646) |
1201 | Unicode UCS-2 Big-Endian |
1250 | ANSI - Central European |
1251 | ANSI - Cyrillic |
1252 | ANSI - Latin I |
1253 | ANSI - Greek |
1254 | ANSI - Turkish |
1255 | ANSI - Hebrew |
1256 | ANSI - Arabic |
1257 | ANSI - Baltic |
1258 | ANSI/OEM - Vietnamese |
1361 | Korean (Johab) |
10000 | MAC - Roman |
10001 | MAC - Japanese |
10002 | MAC - Traditional Chinese (Big5) |
10003 | MAC - Korean |
10004 | MAC - Arabic |
10005 | MAC - Hebrew |
10006 | MAC - Greek I |
10007 | MAC - Cyrillic |
10008 | MAC - Simplified Chinese (GB 2312) |
10010 | MAC - Romania |
10017 | MAC - Ukraine |
10021 | MAC - Thai |
10029 | MAC - Latin II |
10079 | MAC - Icelandic |
10081 | MAC - Turkish |
10082 | MAC - Croatia |
12000 | Unicode UCS-4 Little-Endian |
12001 | Unicode UCS-4 Big-Endian |
20000 | CNS - Taiwan |
20001 | TCA - Taiwan |
20002 | Eten - Taiwan |
20003 | IBM5550 - Taiwan |
20004 | TeleText - Taiwan |
20005 | Wang - Taiwan |
20105 | IA5 IRV International Alphabet No. 5 (7-bit) |
20106 | IA5 German (7-bit) |
20107 | IA5 Swedish (7-bit) |
20108 | IA5 Norwegian (7-bit) |
20127 | US-ASCII (7-bit) |
20261 | T.61 |
20269 | ISO 6937 Non-Spacing Accent |
20273 | IBM EBCDIC - Germany |
20277 | IBM EBCDIC - Denmark/Norway |
20278 | IBM EBCDIC - Finland/Sweden |
20280 | IBM EBCDIC - Italy |
20284 | IBM EBCDIC - Latin America/Spain |
20285 | IBM EBCDIC - United Kingdom |
20290 | IBM EBCDIC - Japanese Katakana Extended |
20297 | IBM EBCDIC - France |
20420 | IBM EBCDIC - Arabic |
20423 | IBM EBCDIC - Greek |
20424 | IBM EBCDIC - Hebrew |
20833 | IBM EBCDIC - Korean Extended |
20838 | IBM EBCDIC - Thai |
20866 | Russian - KOI8-R |
20871 | IBM EBCDIC - Icelandic |
20880 | IBM EBCDIC - Cyrillic (Russian) |
20905 | IBM EBCDIC - Turkish |
20924 | IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol) |
20932 | JIS X 0208-1990 & 0121-1990 |
20936 | Simplified Chinese (GB2312) |
21025 | IBM EBCDIC - Cyrillic (Serbian, Bulgarian) |
21027 | Extended Alpha Lowercase |
21866 | Ukrainian (KOI8-U) |
28591 | ISO 8859-1 Latin I |
28592 | ISO 8859-2 Central Europe |
28593 | ISO 8859-3 Latin 3 |
28594 | ISO 8859-4 Baltic |
28595 | ISO 8859-5 Cyrillic |
28596 | ISO 8859-6 Arabic |
28597 | ISO 8859-7 Greek |
28598 | ISO 8859-8 Hebrew |
28599 | ISO 8859-9 Latin 5 |
28605 | ISO 8859-15 Latin 9 |
29001 | Europa 3 |
38598 | ISO 8859-8 Hebrew |
50220 | ISO 2022 Japanese with no halfwidth Katakana |
50221 | ISO 2022 Japanese with halfwidth Katakana |
50222 | ISO 2022 Japanese JIS X 0201-1989 |
50225 | ISO 2022 Korean |
50227 | ISO 2022 Simplified Chinese |
50229 | ISO 2022 Traditional Chinese |
50930 | Japanese (Katakana) Extended |
50931 | US/Canada and Japanese |
50933 | Korean Extended and Korean |
50935 | Simplified Chinese Extended and Simplified Chinese |
50936 | Simplified Chinese |
50937 | US/Canada and Traditional Chinese |
50939 | Japanese (Latin) Extended and Japanese |
51932 | EUC - Japanese |
51936 | EUC - Simplified Chinese |
51949 | EUC - Korean |
51950 | EUC - Traditional Chinese |
52936 | HZ-GB2312 Simplified Chinese |
54936 | Windows XP: GB18030 Simplified Chinese (4 Byte) |
57002 | ISCII Devanagari |
57003 | ISCII Bengali |
57004 | ISCII Tamil |
57005 | ISCII Telugu |
57006 | ISCII Assamese |
57007 | ISCII Oriya |
57008 | ISCII Kannada |
57009 | ISCII Malayalam |
57010 | ISCII Gujarati |
57011 | ISCII Punjabi |
65000 | Unicode UTF-7 |
65001 | Unicode UTF-8 |
Identifier | Name |
1 | ASCII |
2 | NEXTSTEP |
3 | JapaneseEUC |
4 | UTF8 |
5 | ISOLatin1 |
6 | Symbol |
7 | NonLossyASCII |
8 | ShiftJIS |
9 | ISOLatin2 |
10 | Unicode |
11 | WindowsCP1251 |
12 | WindowsCP1252 |
13 | WindowsCP1253 |
14 | WindowsCP1254 |
15 | WindowsCP1250 |
21 | ISO2022JP |
30 | MacOSRoman |
10 | UTF16String |
0x90000100 | UTF16BigEndian |
0x94000100 | UTF16LittleEndian |
0x8c000100 | UTF32String |
0x98000100 | UTF32BigEndian |
0x9c000100 | UTF32LittleEndian |
65536 | Proprietary |
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.
This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
FIPS mode can be enabled by setting the UseFIPSCompliantAPI configuration setting to True. This is a static setting that applies to all instances of all components of the toolkit within the process. It is recommended to enable or disable this setting once before the component has been used to establish a connection. Enabling FIPS while an instance of the component is active and connected may result in unexpected behavior.
For more details, please see the FIPS 140-2 Compliance article.
Note: This setting is applicable only on Windows.
Note: Enabling FIPS compliance requires a special license; please contact sales@nsoftware.com for details.
Setting this configuration setting to True tells the component to use the internal implementation instead of using the system security libraries.
This setting is set to False by default on all platforms.
Trappable Errors (OFTPClient Component)
OFTPClient Errors
671 | OFTP protocol error. |
672 | Server supplied an invalid SSID code. |
673 | Server supplied an invalid SFID code. |
674 | Server supplied an invalid password. |
675 | Server returned an invalid client SSID code. |
676 | Server returned an invalid client SFID code. |
677 | Server returned an invalid client password. |
678 | "Error building packet to send." |
679 | Error reading files specified. |
680 | Invalid date timestamp. |
681 | Local file exists and overwrite is set to false. |
682 | Invalid hash value. |
683 | Invalid signature. |
684 | Cryptographic operation failed. |
685 | No encryption certificate was specified. |
686 | No signing certificate was specified. |
687 | Send failed. Check the description for more details. |
688 | The requested feature is only supported in OFTP Version 2.0. Check the description for more details. |
689 | A required certificate was not provided. The error descriptions indicates which property must be set. |
690 | Invalid Certificate. |
691 | Failed to import trusted certificates. |
TCPClient Errors
100 | You cannot change the RemotePort at this time. A connection is in progress. |
101 | You cannot change the RemoteHost (Server) at this time. A connection is in progress. |
102 | The RemoteHost address is invalid (0.0.0.0). |
104 | Already connected. If you want to reconnect, close the current connection first. |
106 | You cannot change the LocalPort at this time. A connection is in progress. |
107 | You cannot change the LocalHost at this time. A connection is in progress. |
112 | You cannot change MaxLineLength at this time. A connection is in progress. |
116 | RemotePort cannot be zero. Please specify a valid service port number. |
117 | You cannot change the UseConnection option while the component is active. |
135 | Operation would block. |
201 | Timeout. |
211 | Action impossible in control's present state. |
212 | Action impossible while not connected. |
213 | Action impossible while listening. |
301 | Timeout. |
302 | Could not open file. |
434 | Unable to convert string to selected CodePage. |
1105 | Already connecting. If you want to reconnect, close the current connection first. |
1117 | You need to connect first. |
1119 | You cannot change the LocalHost at this time. A connection is in progress. |
1120 | Connection dropped by remote host. |
TCP/IP Errors
10004 | [10004] Interrupted system call. |
10009 | [10009] Bad file number. |
10013 | [10013] Access denied. |
10014 | [10014] Bad address. |
10022 | [10022] Invalid argument. |
10024 | [10024] Too many open files. |
10035 | [10035] Operation would block. |
10036 | [10036] Operation now in progress. |
10037 | [10037] Operation already in progress. |
10038 | [10038] Socket operation on nonsocket. |
10039 | [10039] Destination address required. |
10040 | [10040] Message is too long. |
10041 | [10041] Protocol wrong type for socket. |
10042 | [10042] Bad protocol option. |
10043 | [10043] Protocol is not supported. |
10044 | [10044] Socket type is not supported. |
10045 | [10045] Operation is not supported on socket. |
10046 | [10046] Protocol family is not supported. |
10047 | [10047] Address family is not supported by protocol family. |
10048 | [10048] Address already in use. |
10049 | [10049] Cannot assign requested address. |
10050 | [10050] Network is down. |
10051 | [10051] Network is unreachable. |
10052 | [10052] Net dropped connection or reset. |
10053 | [10053] Software caused connection abort. |
10054 | [10054] Connection reset by peer. |
10055 | [10055] No buffer space available. |
10056 | [10056] Socket is already connected. |
10057 | [10057] Socket is not connected. |
10058 | [10058] Cannot send after socket shutdown. |
10059 | [10059] Too many references, cannot splice. |
10060 | [10060] Connection timed out. |
10061 | [10061] Connection refused. |
10062 | [10062] Too many levels of symbolic links. |
10063 | [10063] File name is too long. |
10064 | [10064] Host is down. |
10065 | [10065] No route to host. |
10066 | [10066] Directory is not empty |
10067 | [10067] Too many processes. |
10068 | [10068] Too many users. |
10069 | [10069] Disc Quota Exceeded. |
10070 | [10070] Stale NFS file handle. |
10071 | [10071] Too many levels of remote in path. |
10091 | [10091] Network subsystem is unavailable. |
10092 | [10092] WINSOCK DLL Version out of range. |
10093 | [10093] Winsock is not loaded yet. |
11001 | [11001] Host not found. |
11002 | [11002] Nonauthoritative 'Host not found' (try again or check DNS setup). |
11003 | [11003] Nonrecoverable errors: FORMERR, REFUSED, NOTIMP. |
11004 | [11004] Valid name, no data record (check DNS setup). |