Authentication

The concept described in this section is available for openFT partners as of V8.1 running on Unix and Windows systems as well as for openFT partners as of V9.0 running on BS2000 and z/OS. This form of authentication is not available for FTAM partners and FTP partners because neither the FTP protocol nor the FTAM protocol that has been standardized by ISO provides a comparable functionality.

If data requiring an extremely high degree of security are to be transferred, it is important that the respective partner system undergo a reliable identity check (“authentication”) before the transfer. The two openFT instances that are engaged in a transfer must be able to mutually check each other using cryptographic means, to ensure that they are connected to the “correct” partner instance.

The openFT concept is based on the addressing of the openFT instances, using a networkwide, unique ID, and the exchange of partner-specific key information.

Please note that authentication is only possible for named partners!