The File Transfer Protocol (FTP) is a standard communication protocol used for the transfer of computer files between a server (for example an OTYS server) and a client (for example a computer using FileZilla). For secure transmission that protects the username and password and encrypts the content, FTP is often secured with SSL/TLS (FTPS) or replaced with SSH File Transfer Protocol (SFTP).
In the OTYS Go! system it is possible to add & retrieve files on various places, for example in the dossier of a candidate. However, in some cases we want to transfer files with our customer (for example in case of an data import or export). For this every customer has some customer specific storage on our server. This can be accessed through:
MyOTYS
SFTP
FTPS
In most cases we advise users to use MyOTYS for this file exchange (since it has its own secure user interface and does not need additional software or authentication), in some cases connecting to FTPS or SFTP makes sense (for example for exchanging very large files or linking a BI tool to the data). Although FTPS is still supported and widely used by our customers, SFTP is the preferred method for new implementations.
This page describes how you can set up SFTP.
About FTP, FTPS & SFTP
FTP, FTPS, and SFTP are all used to transfer files between systems, for example when exchanging files with a customer, supplier, or another application. The important difference is how securely those files and login credentials are transferred.
FTP
FTP is the traditional way of transferring files which normally uses port 21. Its main disadvantage is that it does not encrypt the connection. This means that usernames, passwords, and transferred data can potentially be intercepted if the network connection is compromised. For that reason, FTP should generally not be used for sensitive or confidential information, and many organizations no longer allow it at all. Think of FTP as sending a postcard: it gets the information to its destination, but the contents aren't protected along the way.
FTPS
FTPS is essentially FTP with an additional security layer: TLS encryption. So FTPS is the secure version of FTP, similar how HTTPS is the secure version of HTTP. The connection is encrypted, protecting both authentication information and the files being transferred. An important practical detail is that FTPS is still based on FTP and therefore still normally uses port 21. Switching from FTP to FTPS is normally from a client perspective very simple (and sometimes even totally unnoticed). Think of FTPS as the familiar FTP delivery service, but now the contents travel in a secure, locked container.
SFTP
Despite the similar name, SFTP is not a secure version of FTP. It is a completely different protocol. SFTP runs over SSH (Secure Shell) and encrypts the complete connection. It normally uses port 22 and can authenticate using a username/password or an SSH key. SFTP is very commonly used for automated integrations and secure file exchanges between organizations. Since it is a completely different protocol, switching from FTP to SFTP does require additional configuration. Think of SFTP as a different secure courier service altogether: it achieves the same goal—transferring files—but uses different technology to do it.
As mentioned above, SFTP is the preferred method for new implementations. At OTYS we only accept authentication with Ed25519 SSH public keys in OpenSSH format.
Setting up an SFTP connection between you and OTYS
If you wish to set up an SFTP connection with us, you will need to generate a private key and a public key on your side. After this, you will share your public key with us, and we will set up your connection. When this is done we will deliver you your username that’s been linked to your public key. From there you can finalize the setup on your side.
Note: please, do not send us your private key. There are essentially no circumstances in which we would request this. If you do, we will ask you to re-generate both keys, and only send us your public key. This type of encryption functions on the fact that any other parties (OTYS in this case) do not have access to your private key.
Acquiring your keys
Requirements
Generating your keys
To create an (Ed25519) SSH key par you can - for example - take the following steps on a windows computer.
Click on the Windows start button;
A search window will appear. Type in ‘cmd’, then press enter;
Command prompt will appear. Type the following, and replace ‘[yourcomment]’ by any comment which will help both parties recognize the key (For example: ‘OTYS SFTP recruitment agency 2026’):
ssh-keygen -t ed25519 -C "[yourcomment]"Press enter;
You will be prompted if you want to use the standard location, which will most likely be ‘C:\Users\[username]\.ssh\id_ed25519’. Here you can hit enter again;
You will be prompted to optionally enter a passphrase. A passphrase provides additional protection for your private key. If you choose to use one, make sure to store it securely, as you may need it when configuring or using your SFTP connection.
The keys will now be stored in the location of step (5).
From here you can send the public key (which in this case ends with '.pub') to the party that manages the SFTP server (in this case OTYS). How to deliver this in a format that works best for a quick and easy set-up can be read below.
Before sending it might be wise to open the public key in Notepad to see if the key looks like what you expect it to look like. If you use a Windows-computer, double clicking the file might try and open Microsoft publisher (because it is in a .pub format). To read the key in Notepad, right click the file, click ‘Open with’, then click ‘Notepad’, or click ‘Choose another app’, then click Notepad. Windows publisher is not needed.
The key below is an example, and not a real key.
Example of what a public key would look like (this is not a real key).
ssh-ed25519 AAAAC3NzaC1lZxI1NTE5AAAAID5R++6OMqO28iT02BgXi2cQO4BkQqS2/XOzfF7gdyBa [yourcomment]
Requesting an SFTP
Once you have your keys (both public and private), you can create a ticket in the OTYS Go! support module, where you can request the setup of an SFTP. Please be so kind to provide us with the public key you’ve generated in the ticket. There is no need to encrypt the key or send it via a service that protects information since it’s just the public key and no other parties have access to the private key. Please, do not send us the private key.
From here, our team will set up your connection.
Once this is done, you will receive your username, as well as a our SFTP host, port & fingerprint which is the same in all cases. You can use your username and your private key to log in.
Testing your SFTP
You can simply log in, and access your files from there. The access to your old FTPS can be closed off by us after the SFTP is set up.
You are not allowed to perform any kind of security or penetration testing without our explicit permission.