It is only possible to encrypt the file contents (i.e. user data) if openFT-CR has been installed. This product is subject to export restrictions and is therefore not available in all countries. On BS2000 systems, the product CRYPT is used for encryption provided that it is installed and running. Otherwise openFT's internal encryption algorithms are used.
The encryption of user data is only available for:
transfer requests with openFT partners
outbound requests via the TLS protocol to a FTP server with Secure FTP support.
If one of the two systems is not capable of handling encrypted file transfers, the request is rejected.
Possible settings for file content encryption
openFT allows you to:
Specifically request the encrypted transfer of your user data on outbound requests
Force or prohibit the encryption of the user data via an admission profile in the case of inbound requests:
Encryption can be explicitly forced, e.g. for requests with particular security implications. Requests without encrypted user data are rejected.
Encryption can be explicitly prohibited, e.g. for requests with reduced security implications for which performance is important. Requests with encrypted user data are rejected.
As FT administrator, you can use operating parameters to force data encryption for all inbound and/or outbound requests or to specify a minimum length of the AES key. If a minimum key length for the RSA and/or the AES key is specified, the behaviour is the same as described in the section “Encryption of the request description data”.
The settings apply to file transfer requests via the openFT protocol as well as for administration requests. FTAM requests and inbound FTP requests are rejected because no encryption is permitted. File management requests are performed without encryption irrespective of the settings. In addition, the following applies:
If outbound encryption is activated then the file content is encrypted on outbound requests even if no encryption is demanded in the request itself. If the partner does not support encryption (e.g. because it is deactivated or because openFT-CR is not installed) then the request is rejected.
If an unencrypted inbound request is to be processed while inbound encryption is activated, then this request is rejected.
Please note that the effort required for encryption in the participating partner systems has a negative impact on performance. This means in particular that both the transfer time of files can become larger and the CPU usage can be increased.