Server Authentication Methods

The remote SFTP servers can be authenticated by either (plain) public-key authentication or certificate authentication. When certificate authentication is used, the public key is included in the certificate that the server sends to the client.

Server Authentication with Public Keys

In (plain) public-key authentication, the server sends its public key to Tectia MFT Events at the beginning of the first connection, and after the user has once verified and accepted the key, it will be used in all future connections to that server.

Tectia MFT Events supports also the legacy OpenSSH public-key format, eliminating the need for manual key conversions in multi-vendor Secure Shell environments. The key-compatibility feature allows easy migration of OpenSSH environments to Tectia.

Server Authentication with Certificates

In certificate authentication, Tectia MFT Events relies on a trusted third party, a certification authority (CA) to verify the server's identity. The signature of the certification authority in the server certificate guarantees the authenticity of the server certificate.

Tectia supports both Certificate Revocation Lists (CRLs) and Online Certificate Status Protocol (OCSP) for centralized revocation of user credentials. CRLs are automatically fetched from a local file or by using HTTP or LDAP, depending on the local settings and the CRL Distribution Point extension in the certificate. CRLs can also be imported offline in legacy environments.

For certificate lifecycle management, Tectia MFT Events has been integrated with Entrust PKI that provides transparent certificate lifecycle management in Entrust environments. Entrust support is available on Windows platforms.

For online certificate enrollment, Tectia MFT Events supports IETF PKIX standards (CMPv2) and Cisco Systems' Simple Certificate Enrollment Protocol (SCEP). Certificates can also be imported by using the PKCS#12 envelope format supported by most Certification Authorities (CAs).