Skip to main content
tiCrypt 2.18.1

SFTP Connections

ResearcherRequires: tiCrypt Connect. SFTP bidirectional also needs a Super-admin to allowlist the server for you or your team.
Permission requirements
  • Vault Files and Directories
    • View their directories and their groups' directories
    • Create files (needed to upload)
    • Upload file content (needed to upload)
    • Add items to directories
    • Get the keys of their files and files shared with them (needed to download)
    • Download the content of files they can access

An SFTP connection is a link that tiCrypt Connect opens from your computer to an SFTP server, signed in with your own account on that server. While the connection is open, the server appears as a drive named SFTP under My Computer in the Vault, and you move files between it and the Vault the same way you move files between the Vault and a folder on your computer. tiCrypt offers two kinds of connection. SFTP inbound only brings files from the server into your Vault. SFTP bidirectional can also send files from your Vault to the server, and works only with servers a Super-admin has approved for you.

An SFTP connection is not an SFTP inbox. An SFTP inbox lets someone without a tiCrypt account send files to you through tiCrypt's own SFTP service. An SFTP connection is you, signed in to tiCrypt, reaching out to an SFTP server someone else runs.

Why there are two kinds of SFTP connection​

Bringing data in and sending data out carry different risks, so tiCrypt gates them differently. A file pulled into the Vault is encrypted on arrival and stays under tiCrypt's protection, so SFTP inbound lets you connect to any server you can reach, with no administrator involved. It follows the same rule as the cloud services under Add new cloud service (Box, Dropbox, Google Drive and OneDrive), which are also pull-only.

A file pushed to an SFTP server leaves tiCrypt's protection. It arrives on the server decrypted, and from then on only that server's own controls protect it. Sending data out is an export decision, so SFTP bidirectional does not let you type a server address. You pick from the servers a Super-admin has registered and allowlisted for you or one of your teams, and tiCrypt checks that grant with the backend every time you connect. Each check is logged.

Without the split, every SFTP server would be an exit. If one kind of connection did both jobs, either any server a user could reach would become a way to move data out of the enclave, or every pull from a collaborator's server would wait on an administrator. Two kinds let the common case, bringing data in, stay self-service while the rare case, sending data out, stays approved and recorded.

Neither kind can change what is already on the server. tiCrypt never deletes, renames, moves or overwrites files on an SFTP server, and it does not create folders there. A bidirectional connection only adds new files to folders that already exist.

SFTP inbound and SFTP bidirectional compared​

The following table describes how the two kinds of connection differ.

SFTP inboundSFTP bidirectional
Icon on the drive Arrow pointing down and to the right Two arrows pointing in opposite directions
DirectionServer to Vault onlyServer to Vault, and Vault to server
Which serversAny server your computer can reach. You enter the host and port.Only servers a Super-admin has registered and allowlisted for you or one of your teams. You pick from a list.
PortYou enter it. The default is 22.Set by the Super-admin with the server.
Sign-inYour user name and password on the serverYour user name and password on the server
Checked by tiCrypt when you connectNoYes. The backend confirms the server is allowlisted for you, and logs the check.
Changes existing files or folders on the serverNeverNever

When to use each kind​

  • SFTP inbound: a collaborator, instrument or data provider makes files available on an SFTP server where you have an account, and you want them in your Vault. No administrator is involved.
  • SFTP bidirectional: you have to deliver results to an approved destination, such as a sponsor's or coordinating center's SFTP server, and a Super-admin has allowlisted that server for you or your team.
  • An SFTP inbox instead: the person sending the data has no tiCrypt account and no SFTP server of their own. Create an SFTP inbox and give them its credentials.
  • SFTP to a VM instead: the data has to land inside a running VM rather than in your Vault. Use the VM's own SFTP access, described in VM File Operations.
  • A cloud service instead: the files are in Box, Dropbox, Google Drive or OneDrive. Use Add new cloud service, described in Transfer.

Before you begin​

  • tiCrypt Connect: it must be running, because it makes the connection. Without it, Connect to SFTP server is unavailable. See tiCrypt Connect.
  • Network access: your computer must be able to reach the server. The connection goes from your computer, not from the tiCrypt servers, so your network, firewall or VPN must allow it.
  • An account on the server: you need your own user name and password on the server. SSH keys are not supported.
  • Allowlisting, for SFTP bidirectional: a Super-admin must register the server and add you, or a team you belong to, to its allowlist. A server past its expiration date no longer appears. See External SFTP Servers.
  • Project access, for pushing tagged files: you must be an active member of the file's project, with permission to download its files.

Connect with SFTP inbound​

  1. Go to the Vault icon in the top left panel.
  2. In the left panel, under My Computer, click Connect to SFTP server.
  3. Select SFTP inbound.
  4. In the Select SFTP inbound credentials pop-up, click Add a new set of SFTP inbound credentials.
  5. In Host, enter the host name or IP address of the SFTP server.
  6. Leave Port at 22 unless the server uses a different port.
  7. Enter your Username and Password on that server.
  8. Click Login.
  9. In Select SFTP inbound drives, keep SFTP ticked and click Accept.
  10. Click Next.
Result:

The Transfer files between My Vault and My Computer window opens. A drive named SFTP with the inbound arrow icon is listed under My Computer, showing the folders your account can see on the server.

The following table describes the fields of the SFTP inbound login form. Login stays disabled until every field is valid.

FieldRules and messages
HostRequired ("You must specify a host name"), at most 120 characters. Enter a full domain name such as sftp.example.edu, or an IPv4 address. Anything else shows "Must be a valid domain name or IP address".
PortRequired ("You must specify a port"). A number from 1 to 65535. It starts at 22.
UsernameRequired ("You must specify a username"), at most 120 characters. A value the form does not accept shows "Must be a valid ID or email".
PasswordYour password on the server. The form does not require it.

If the server refuses the connection, the pop-up shows the message from tiCrypt Connect, or "Could not connect to SFTP server".

Connect with SFTP bidirectional​

Location: Vault > My Computer > Connect to SFTP server

  1. Select SFTP bidirectional.
  2. In the Select SFTP bidirectional credentials pop-up, click Add a new set of SFTP bidirectional credentials.
  3. In Select SFTP server, choose the server. Each entry shows its name and "host · port", and the hint reads "Select the SFTP server from the list". Servers past their expiration date are not listed. If you click Login without choosing one, the pop-up shows "No server selected".
  4. Enter your Username and Password on that server.
  5. Click Login.
  6. In Select SFTP bidirectional drives, keep SFTP ticked and click Accept.
  7. Click Next.
Result:

The Transfer files between My Vault and My Computer window opens. A drive named SFTP with the two-arrow icon is listed under My Computer. Files can now move in both directions between it and the Vault.

note

Only servers allowlisted for you, or for a team you belong to, appear in Select SFTP server. If the server you need is missing, or the pop-up reads "No SFTP servers are currently available", ask a Super-admin to allowlist it.

Pull files from an SFTP server into the Vault​

This procedure describes how to copy files from the server into the Vault. It works with both kinds of connection.

Location: Vault > My Computer > Transfer files between My Vault and My Computer

  1. In the right panel of the new window, open the SFTP drive and go to the files or folders you want.
  2. In the left panel, open the Vault directory that should receive them, for example My Files or a group directory.
  3. Drag the files or folders from the right panel onto the Vault directory in the left panel.
  4. In the Upload ... to the Vault? pop-up, review the preview and click Upload.
Result:

The files appear in the Vault directory you chose, encrypted like any other upload. Folders keep their structure. The progress shows as an Uploading files task. The files on the SFTP server are unchanged.

tip

You can also pull without the transfer window. On the Vault page, click a folder of the SFTP drive under My Computer so its files show on the right, then drag them onto a Vault folder in the left tree. See Vault File Tree.

Push files from the Vault to an SFTP server​

This procedure describes how to send files from the Vault to the server. It works only with an SFTP bidirectional connection.

Pushed files leave tiCrypt's protection

Files arrive on the SFTP server decrypted. From then on only that server's controls protect them. Push only data you are authorized to export to that destination.

Location: Vault > My Computer > Transfer files between My Vault and My Computer

  1. In the right panel of the new window, open the SFTP drive with the two-arrow icon and go to the destination folder.
  2. In the left panel, select the Vault files you want to send.
  3. Drag the files onto the destination folder in the right panel.
  4. In the Download ... to your computer? pop-up, review the preview and click Download.
Result:

The files are written to the destination folder on the SFTP server. The progress shows as a Downloading files task. The originals stay in your Vault.

tip

You can also push without the transfer window. On the Vault page, open the Vault folder that holds the files, then drag them from the file list onto the destination folder of the SFTP drive under My Computer in the left tree.

note
  • Send files, not folders: tiCrypt cannot create folders on an SFTP server. If you drag a folder, it fails with "Failed to create directory ... in destination" and none of its files are sent. Create the folder on the server with your own SFTP client first, then send the files into it.
  • Name conflicts: if the destination already holds a file with the same name, the new copy is given a numbered name, such as results (1).csv. Existing files are never overwritten.
  • Why the pop-up says "Download": tiCrypt treats a push as a download through tiCrypt Connect. The same warning, project checks and download record apply, but the files go to the SFTP server instead of your disk.

What happens next​

  • Pulled files: tiCrypt Connect reads each file from the server and encrypts it on your computer before it is uploaded. In the Vault it is an ordinary encrypted file that you can share, tag or move into a VM like any other.
  • Pushed files: tiCrypt Connect fetches each file from the Vault, decrypts it in memory and streams it to the server without saving a copy on your computer. Files tagged with a project are skipped unless you are an active member of that project with permission to download its files.
  • Connection checks: for SFTP bidirectional, the backend confirms the server is allowlisted for you each time you connect and logs the result. A server whose allowlist no longer includes you refuses the next connection.
  • How long a connection lasts: tiCrypt Connect keeps the connection open while it runs and does not save your SFTP password. After you close tiCrypt Connect, connect again. Signing in again to the same server with the same user name replaces the earlier connection.

Disconnect from an SFTP server​

Location: Vault > My Computer > Connect to SFTP server

  1. Select SFTP inbound or SFTP bidirectional, whichever you connected with.
  2. On the card for your account, click the Delete credential button.
  3. Click Cancel to close the pop-up. Next also closes it, but then opens the transfer window.

Delete credential acts at once, without confirmation. You can also sign out of the server from the settings button next to My Computer: open Credentials, select the account and choose Logout. See Transfer.

Result:

The SFTP drive is removed from My Computer and tiCrypt Connect closes the connection to the server. Files already pulled into the Vault, or pushed to the server, are not affected.

Confirmations, Errors & Solutions
SFTP Inbound Notice

Data flows inbound only.

SFTP Bidirectional Notice

Data flows inbound and outbound. If the specific server you need does not appear, please contact your system administrator.

Missing Field

You must specify a host name / You must specify a port / You must specify a username

Complete the Form

Fill in the field named in the message. Login stays disabled until the form is complete.

Cannot Reach or Sign In to the Server

unable to connect to [host:port]: reason

Check the Address, Network and Credentials

Check the host, port, user name and password. The connection is made from your computer, so confirm that your network or VPN can reach the server. If the reason mentions authentication, the user name or password was refused by the server.

No Approved Servers

No SFTP servers are currently available. Please contact your system administrator.

Ask a Super-admin to Allowlist the Server

No server is allowlisted for you or your teams, or every allowlisted server has expired. Ask a Super-admin to add you or your team to the server's allowlist in Management > External SFTP Servers.

Server Not Allowed

sftp not allowed for [host:port]

Ask a Super-admin to Confirm the Allowlist

The backend refused the connection because the server's allowlist does not include you or any of your teams. Admins see every registered server in the list but can connect only to the ones allowlisted for them. Ask a Super-admin to update the allowlist.

Drop Refused on a Read-Only Drive

You cannot put files here because SFTP is read-only

Use SFTP Bidirectional

SFTP inbound drives and cloud service drives only accept pulls, so tiCrypt refuses the drop before anything is sent. To send files to a server, connect to it with SFTP bidirectional.

Folder Not Created on the Server

Failed to create directory /folder-name/ in destination

Send the Files Instead of the Folder

tiCrypt cannot create folders on an SFTP server. Create the folder on the server with your own SFTP client, then send the files inside it.

Skipping Project Files

Skipping /file-name: you are not an active member of project-name

Activate the Project or Ask the Project Manager

Make sure the project is active in your session. If it is, ask the project manager to add you to the project with permission to download its files.