SFTP File Automation Options

An SFTP server is included with every Rithum account, each having its own unique SFTP credentials. The directories below are created for every SFTP account and for every account record created in the platform. The directories will house the files used to retrieve and deposit data associated with the automated jobs you’ll create. For more information about creating automated jobs, see Creating an Automated Job.

Ready to access the SFTP page in the portal? Go to https://app.dsco.io/automation/sftp.

For more information about your account-specific SFTP credentials, see Your SFTP Site Credentials.

 

The following directories are available for every SFTP account.

Directory
 Description
/in/ Used to store files to be processed by the platform (if you choose to reference the Rithum SFTP instance instead of another URL for automated file-processing).
/in/processing/ Used to store files that are currently being processed by the platform. Once the files are processed, they will be moved to the /in/archive/ folder.
/in/archive/ Used to store files from the /in/ folder that have been processed by the platform. You’ll have access to the files in /in/archive/ folder for 60 days.
/out/ Used to store files that have been exported from the  platform (if you choose to reference the Rithum SFTP instance instead of another URL for automated file-processing).
/out/archive/ Used to store files that you’ve downloaded from the /out/ folder. You’ll have access to the files in /out/archive/ for 60 days.
/misc/ Used to temporarily store files. No automation is used with this folder.

 

Rithum also supports the use of external SFTP servers for all incoming and outgoing operations. Additionally, if a job is configured as an import, Rithum supports the use of both HTTP and HTTPS file-path URLs.

Using Identity Keys instead of Whitelisting IP Addresses

Trading partners can use our public keys to verify the identify of our servers. While this is configured differently for different SFTP clients, you can find the necessary information regarding what we support and our public keys when configuring the use of identity keys with the Platform SFTP servers.

The public keys for Rithum servers are below. While SSH supports multiple key types, we recommend using ED25519. To confirm that these are ED25519 keys, refer to the ssh-ed25519 prefix.

Production

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMARMCy7o7wub7kewRWCqxD0mb8jz5wibtK7hRYcNHv0
Staging

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOnta2KQAh7e/clxfypuSuPmyI/lXEOmk/H0QoBChpPy

Rithum also supports RSA public keys. Be aware that RSA keys are subject to change at any time, which may require configuration updates from most SFTP partners. Here are the Rithum RSA public keys.

Production ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDdcEEDx9FJH9olVIdkrpdJ5xm21l0+8ZI00Papc9tgSFaMr77jGEofkqq1WcdoQrdNCt+3QuhNo79wUidZRNQFb0oQHZ4oB6qi0cJnNhxRJWSr3v+y58RHnJhac3v+MOiT4Wq/GDiU1ubtsI4kSlzOv7w7AO2QAUQiaDoy4VZdg+eZIJHk+Sh22V5GQlwJ7wGdmlqEGSIm3/vd6qyG0oF7faB6JsWrXYbyzmf/taFdl8VBOi6iINX68qUdrUQeH0o7tqxnPDGruM8fbMQsz5BWVf9g/vS1pEo85yzF7cd+AZYSBImwGk/TVnme10X04IO+l9lD0q2sMppDqLRG7Acz
Staging ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAABAQDSUhRlZhem1xuvvd9J72Pfyisvy1+fVTQqblDYKUkuQk2IBm4t18RWXckdLdL4TbsS4lo2uHLRVwrbcKo/8aKTsq45G2cscRURtMr12uH01aOBcrg18vMtUxfJcQp6la8dYvwvlbby7jrJiszEebTMjr4g2mlX3ifHNj7qSFj3xzNXkA3BlUKB8nuSWhA/vRfOSrI2kCzzront33+Gy/hCR2DMV8eUZ1odATPLIJ+/RD2zqHL1fbhnPl1kLkScNgVLAkaNPFV3Z9uDtjw1jhcBQNj/zhkUV62Rq4Zo6OvpOQzGc9AyaGxHgsdtLNEPcmGwT0uIRVdLP3fPuC+hQqHV

Additionally, Rithum supports ECDSA keys. You can find these below:

Production ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBDMDUnviJapIzvt6Ic4LcxiP2CfdMLNq60U+H8m8GZB9ryZ9SYx+JO8yIhL+i2NIBFcWOauRhI1sAjYoagTihtw=
Staging ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBDVz68YoS5i8b9Bl3BZjAJ0oxzpJyDQTLEPpWJTfc9+iYam/a+fFwHEgdBr+CNbslDzGQE7WH7Wyq9XNuQdkeRk=

Supported Ciphers

Ciphers

  • aes256-gcm@openssh.com
  • chacha20-poly1305@openssh.com
  • aes256-ctr
  • aes128-gcm@openssh.com
  • aes128-ctr

MACs

  • hmac-sha2-256-etm@openssh.com
  • hmac-sha1-etm@openssh.com
  • umac-128-etm@openssh.com
  • hmac-sha2-512-etm@openssh.com
  • hmac-sha2-256
  • hmac-sha1
  • umac-128@openssh.com
  • hmac-sha2-512

Key Algorithms

  • curve25519-sha256
  • curve25519-sha256@libssh
  • org,ecdh-sha2-nistp256
  • ecdh-sha2-nistp384
  • ecdh-sha2-nistp521
  • diffie-hellman-group-exchange-sha256
  • diffie-hellman-group14-sha256
  • diffie-hellman-group16-sha512
  • diffie-hellman-group18-sha512

Host Key Algorithms

  • ssh-ed25519 (preferred)
  • rsa-sha2-256
  • rsa-sha2-512

Public Key Accepted Algorithms

  • ecdsa-sha2-nistp256
  • ecdsa-sha2-nistp256-cert-v01@openssh.com
  • sk-ecdsa-sha2-nistp256@openssh.com
  • sk-ecdsa-sha2-nistp256-cert-v01@openssh.com
  • ecdsa-sha2-nistp384
  • ecdsa-sha2-nistp384-cert-v01@openssh.com
  • ecdsa-sha2-nistp521
  • ecdsa-sha2-nistp521-cert-v01@openssh.com
  • ssh-ed25519 (preferred)
  • ssh-ed25519-cert-v01@openssh.com
  • sk-ssh-ed25519@openssh.com
  • sk-ssh-ed25519-cert-v01@openssh.com
  • rsa-sha2-256
  • rsa-sha2-256-cert-v01@openssh.com
  • rsa-sha2-512
  • rsa-sha2-512-cert-v01@openssh.com

Required RSA Size

  • Keys smaller than 2048 bytes are not allowed.

 

 

 

 

Was this article helpful?
1 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Articles in this section