Skip to main content

Remote SFTP Server

A Remote SFTP Server is a type of Endpoint that represents an external (remote) SFTP server. UDMG uses this Endpoint when acting as an SFTP client to connect to a partner's server. The Endpoint stores connection details such as hostname, port, and authentication credentials, and is used to initiate outbound SFTP transfers. Within a Pipeline, a Remote SFTP Endpoint can function as either a Source (to pull files) or a Destination (to push files), enabling secure and automated file exchanges with remote SFTP servers.

info

File transfers when UDMG is acting as the client are only initiated via the Transfer API (not via the UI).

A Pipeline with a Remote SFTP Server Endpoint cannot be associated with an Account via an Account Group. The Credentials needed to connect and authenticate with an external SFTP server are added at the Pipeline level.

Before You Begin

IP Address/Port

The IP/Port is the combination to connect to the external SFTP server. Obtain the IP Address and Port from your partner. After configuring an Endpoint, always use the Validate button to see if the system can connect to the external SFTP server via the IP/port combination provided. See Validating the Configuration for steps.

Public Key

Each Remote SFTP Server Endpoint must be associated with a single Public Key, which serves as the Host Key of the external SFTP server. This key is used by UDMG to authenticate the server during the SSH connection, ensuring the server's identity and protecting against man-in-the-middle attacks.

You must obtain the Host Key from your partner. To select it during Endpoint creation, a Credential with Credential Type: Public Key must first be created on the Credentials page.

Authentication Credentials at the Pipeline Level

While the Remote SFTP Server Endpoint requires the external server's Public Host Key to verify its identity (configured at the Endpoint level), client authentication credentials are configured separately at the Pipeline level. This design allows reusing the same Endpoint with different credentials across multiple Pipelines.

info

Adding an Endpoint

To add an Endpoint, follow these steps:

  1. From the Sidebar, select Configuration > Endpoints.
  2. Click the Add Endpoint button.
  3. Select Remote SFTP Server as the Endpoint Type.
  4. Complete the Name and Description details for the new Endpoint.
  5. Enter the IP Address and Port you obtained earlier.
  6. Select the host key you created earlier from the Credentials Name dropdown
  7. Optionally select ciphers and other algorithms, or use the default, using the table below as a guide.
  8. Choose whether the Endpoint should be enabled effective immediately.
    info

    The Endpoint still must be added to a Pipeline for the Endpoint to be serviceable.

  9. Click Add.
  10. Validate the connection (connection only, no authentication). See Validating the Configuration.

Field Descriptions

The following table describes the fields that are configured for the Endpoint:

NameDescriptionSpecificationsRequired
Endpoint Type

The type of Endpoint indicates the type of file transfer.

Select: Remote SFTP Server.

The type Cannot be modified after creation.Yes
NameThe name of the Endpoint.Yes
DescriptionThe description of the Endpoint.No
IP AddressThe IP Address of the external SFTP server. Provided by the partner.Must be in IPv4 format.Yes
PortThe port number of the external SFTP server. Provided by the partner.Must be within 1 and 65535.Yes
Credentials Name (Host Key)The name of the Public Key representing the external SFTP server's Host Key.Must reference an already created Public Key.Yes
Key Exchange Algorithms

The allowed key exchange algorithms.

Options (multi-select):

  • ecdh-sha2-nistp521
  • ecdh-sha2-nistp384
  • ecdh-sha2-nistp256
  • curve25519-sha256
  • diffie-hellman-group16-sha512
  • diffie-hellman-group14-sha256
  • curve25519-sha256@libssh.org

Defaulted to:

  • ecdh-sha2-nistp521
  • ecdh-sha2-nistp384
  • ecdh-sha2-nistp256
  • curve25519-sha256
  • diffie-hellman-group16-sha512
No
Ciphers

The allowed ciphers.

Options (multi-select):

  • aes-256-ctr
  • aes-192-ctr

Defaulted to:

  • aes-256-ctr
  • aes-192-ctr
No
MACs

The allowed Message Authentication Codes (MACs).

Options (multi-select):

  • hmac-sha2-256-etm@openssh.com
  • hmac-sha2-512-etm@openssh.com
  • hmac-sha2-256
  • hmac-sha2-512
  • hmac-sha2-1

Defaulted to:

  • hmac-sha2-256-etm@openssh.com
  • hmac-sha2-512-etm@openssh.com
  • hmac-sha2-256
  • hmac-sha2-512
  • hmac-sha2-1
No
Enabled Endpoint

Endpoint's enabled status.

See Enabling and Disabling Endpoints.

Default value: Enabled.Yes

Editing an Endpoint

Endpoint configuration changes are pushed to all Pipelines referencing the Endpoint with immediate effect.

To edit an Endpoint, follow these steps:

  1. From the Sidebar, select Configuration > Endpoint.
  2. Click the Endpoint Name you want to edit.
  3. Click the Edit button above the Endpoint details.
  4. Edit details for the Endpoint, using the Field Descriptions table as a guide.
  5. Click Update.

Managing an Endpoint

Viewing Endpoint Details

To view the details of an Endpoint, follow these steps:

  1. From the Sidebar, click Configuration > Endpoints.
  2. Click the Endpoint Name you want to view.

Endpoint details include all parameters given in the Field Descriptions table above, plus the following read-only metadata:

Endpoint Metadata

NameDescription
UUIDUniversally Unique Identifier of this Endpoint.
VersionVersion number of the configuration. Every change increases the number.
EnabledEndpoint's Enabled status. If enabled, field is set to True.
CreatedDate and time this Endpoint was created.
UpdatedDate and time this Endpoint was last updated.
Test Status

Status of the Validate Endpoint configuration test.

Options:

  • Test not executed
  • Test passed
  • Test error

Validating the Configuration

The Endpoint configuration can be validated to confirm if an unauthenticated connection with the external SFTP server can be made. After clicking the Validate button, one of the following messages appears:

  • Error/Fail: 'Endpoint test has failed. The dial tcp 0.0.0.4:2235: i/o timeout.'
    • If validation fails, then the system was not able to make a successful connection with the external SFTP server. Check the Endpoint's configuration, network path, firewall rules, and try again.
  • Pass: 'Endpoint has passed the test.'
    • If validation passes, then the system was able to make a successful connection with the external SFTP server.

Enabling and Disabling Endpoints

Remote SFTP Server Endpoints can be Enabled or Disabled to control their active status and ability to participate in file transfers.

  • Enabled (default): The Endpoint is active and can participate in file transfers.
  • Disabled: The Endpoint is inactive and cannot participate in file transfers.

To enable or disable an Endpoint, follow these steps:

  1. From the Sidebar, select Configuration > Endpoints.
  2. Click the Endpoint Name of the Endpoint you want to enable/disable.
  3. Click Edit.
  4. If the Endpoint is currently enabled, you can disable the Endpoint by moving the toggle to the left.
  5. Click Update.
info

Changes to the Endpoint's Enabled/Disabled status are not active until the file transfer is scheduled and triggered.

Editing an Endpoint

To edit an Endpoint, follow these steps:

  1. From the Sidebar, select Configuration > Endpoints.
  2. Click the Endpoint Name of the Endpoint you want to edit.
  3. Click the Edit button above the Endpoint details.
  4. Edit details for the Endpoint using the Field Descriptions table as a guide.
  5. Click Update.
  6. Click the Validate button following the above instructions.

Deleting an Endpoint

To delete an Endpoint, follow these steps:

  1. From the Sidebar, select Configuration > Endpoints.
  2. Click the Endpoint Name of the Endpoint you want to delete.
  3. Click the Delete button above the Endpoint details.
  4. You will be asked to confirm the deletion. Click Delete.
warning

UDMG prevents the deletion of a Configuration Item if it is currently referenced by another Configuration Item (i.e., Pipeline). The Configuration Item must be edited or the reference removed before you can delete the Endpoint. Deletion cannot be undone.