UDMG as Gateway
When UDMG acts as a Gateway, it streams files between partners via local server Endpoints (SFTP, FTP, or HTTPS) and remote cloud storage providers (cloud providers), bridging file transfers across any supported protocol to cloud storage.
In this model, UDMG exposes server Endpoints that allow partners to connect using their preferred client or a web browser, depending on the protocol. Transfers are executed based on a defined Pipeline configuration, which determines how files are handled once received.
Access to UDMG as Gateway Pipelines is controlled through Account-based authentication. External partners connect using protocol-specific credentials associated with configured Accounts and Account Groups.
These Pipelines support file uploads and, depending on the protocol and permissions, may also allow file downloads and folder management operations. In all cases, the Remote Cloud Storage Endpoint is used as the destination for files received through the server Endpoint.
Unlike UDMG as Client Pipelines, where transfers must be explicitly initiated through an API request, UDMG as Gateway Pipelines are triggered by external partner actions, such as connecting to the local server Endpoint and performing file operations.
Supported Pipelines
| Pipeline Name | Source Endpoint | Destination Endpoint | Description | Transfer Triggered By |
|---|---|---|---|---|
| Local FTP(S) Server to Remote Cloud Storage | Local FTP(S) Server | Remote Cloud Storage | File transfer configuration where UDMG receives files via FTP(S) and transfers them to a cloud provider. | Partner's FTP(S) client |
| Local HTTPS Server to Remote Cloud Storage | Local HTTPS Server (WTC) | Remote Cloud Storage | File transfer configuration where UDMG receives files via the Web Transfer Client (WTC) and transfers them to a cloud provider. | Partner actions performed through the WTC |
| Local SFTP Server to Remote Cloud Storage | Local SFTP Server | Remote Cloud Storage | File transfer configuration where UDMG receives files via SFTP and transfers them to a cloud provider. | Partner's SFTP client |
Account Authentication
UDMG as Gateway Pipelines are integrated with the Account and Account Group model to control access:
In this scenario, your partners (such as customers, vendors, organizations, departments, internal/external users, or automated systems) connect to UDMG using Accounts (protocol-specific credentials), and access is controlled by the Account Groups they belong to. Each Account Group is associated with one or more Pipelines, which define the available file transfer paths.
This integration ensures that:
- Only authenticated Accounts can initiate connections.
- Each Account can only access the Pipelines explicitly assigned through its Account Groups.
- Access control is enforced at the file transfer level without requiring external firewall or directory-based restrictions.
UDMG as Client Pipelines are not Account-based and do not integrate with the Account and Account Group model. These Pipelines are triggered using UDMG's Transfers Scheduled API.
Permissions
UDMG as Gateway Pipelines support permission-based access control to define what operations an Account can perform when interacting with the cloud provider through a local server Endpoint.
Permissions are configured at the Pipeline level. These permissions determine which file and folder operations are allowed when a partner connects to UDMG.
The available permissions are:
- Download/Read File
- Upload/Write File
- Overwrite File
- Delete File
- List File
- Make Directory
- Remove Directory
- Rename File
- Share File
Not all permissions are available for every Pipeline type. The supported operations depend on the protocol. For details on permission availability, refer to the corresponding Pipeline page.