Skip to main content
Skip table of contents

Basics of the Certificate Managemente

The certificate management system stores which private keys and certificates are to be used or are permitted to be used.

From version 2.7 Build 55 onwards, it is possible to specify the intended use *OFTP more precisely. The alternative special values are listed below. In addition, the certificate management system can be used for partner profiles.

When are entries in the certificate management system required?

An *SSL entry for the trust store is not required in certificate management. The trust store is stored in the corresponding profile (entering the keystore in CERTADMIN) or specified as a parameter in the command because it must be known before the connection is established.

OFTP2 server

The server profile (*RECEIVE) to be started and the client profiles (*SEND) of the corresponding remote stations require the following entries:

An *SSL key entry for the keystore *RECEIVE is required

  • if the connection is to be encrypted with SSL.

An *OFTP key entry for the keystore *RECEIVE is required

  • if OFTP authentication is used (alternative: *OFTPAUTH).

  • if the file is transferred in encrypted form (alternative: *OFTPFILEN).

An *OFTP certificate entry for the truststore *SEND is required

  • if OFTP authentication is used (alternative: *OFTPAUTH).

  • if the file is signed (alternative: *OFTPFILSI).

  • if the end-to-end response is signed (alternative: *OFTPEERP).

Using the STROFTP2 command

The specified server profile (*RECEIVE) and client profile (*SEND) as the remote station require the following entries:

An *SSL key entry for the *RECEIVE keystore is required

  • if the SSL connection requires client authentication.

An *OFTP key entry for the keystore *RECEIVE is required

  • if OFTP authentication is used (alternative: *OFTPAUTH).

  • if the file is signed (alternative: *OFTPFILSI).

  • if the end-to-end response is signed (alternative: *OFTPEERP)

An *OFTP certificate entry for the truststore *SEND is required

  • if OFTP authentication is used (alternative: *OFTPAUTH).

  • if the file is transferred in encrypted form (alternative: *OFTPFILEN).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.