UDMG as Server
When UDMG acts as a Server, it receives file transfers from external partners through supported protocols.
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 Server Pipelines is controlled through Account-based authentication, where external partners connect using protocol-specific credentials associated with configured Accounts and Account Groups.
UDMG as Server Pipelines support file uploads and, depending on the protocol and permissions, may also allow file downloads and folder management operations. In all cases, the Local Filesystem 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 Server Pipelines are triggered by external partner actions, such as connecting to the server Endpoint and performing file operations.
Supported Pipelines
| Pipeline Name | Source Endpoint | Destination Endpoint | Description |
|---|---|---|---|
| Local AS2 Server to Local Filesystem | Local AS2 Server | Local Filesystem | Receives messages from a partner's AS2 client and writes them to the local filesystem. |
| Local FTP(S) Server to Local Filesystem | Local FTP Server | Local Filesystem | Transfers files between a partner's FTP(S) client and the local filesystem. |
| Local HTTPS Server to Local Filesystem | Local HTTPS Server (WTC) | Local Filesystem | Allows partners to upload, download, and manage files and folders through the Web Transfer Client (WTC), with files stored in the local filesystem. |
| Local SFTP Server to Local Filesystem | Local SFTP Server | Local Filesystem | Transfers files between a partner's SFTP client and the local filesystem. |
Account Authentication
UDMG as Server Pipelines are integrated with the Account and Account Group model to control access:
In this scenario, Accounts connect to UDMG using 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 Server Pipelines support permission-based access control to define what operations an Account can perform when interacting with the Local Filesystem through a 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.