Skip to main content
Developer Communities Admin
Community Manager
September 15, 2026

Is SSH available for inbound files?

  • September 15, 2026
  • 2 replies
  • 0 views

Originally posted by Barbara Buchanan on May 12, 2026 at 1:40 PM.

 

Is SSH available for inbound files?

 

The transmission setup for inbound files does not provide a place to add a vendor SSH public key. Is that something that can be added via a case? Thanks all!

    2 replies

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Thibaut Etiembre on May 25, 2026, 9:02 AM.

     

    Hi Barbara,

     

     

    For inbound files, Integration Studio relies on the general Dayforce SFTP configuration. It is possible to connect to Dayforce SFTP using SSH keys instead of username and password. You would first need to create your set of keys and open a ticket with our support team for these to be entered in your sftp for your namespace.

     

    Regards,

    Thibaut

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Frank Ruffolo on May 26, 2026, 2:03 PM.

     

    Just to add to Thibaut's comment, our internal team advised the following:

     

    SSH key authentication can be used for Dayforce SFTP access. The SSH key setup is not configured within Integration Studio itself; it is managed as part of the Dayforce SFTP account configuration.

     

    To request this, the customer or partner should work through their normal Dayforce support/contact channel and provide the following details:

    • Environment: Production, Test, Implementation, etc.
    • SFTP username/account, if already known
    • Target folder or integration path, if applicable
    • Vendor or partner contact details
    • The SSH public key to be added
    • Whether the key is for a new setup, a replacement key, or an additional key

     

    Please do not send the private key. The private key should remain with the vendor/partner. Dayforce only needs the public key.

     

    File-level PGP encryption, if required, is separate from SSH key authentication and should be confirmed as part of the integration setup.