Panel | |
---|---|
|
Panel | |
---|---|
|
Universal Data Mover Gateway release 2.0.0.0 - May 31, 2024, contains the following high-level features. For a complete list of all the included features and fixes, please refer to Universal Data Mover Gateway 2.0.x Maintenance.
File Transfer Enhancements
Backlog | Title | Description | ||
---|---|---|---|---|
B-18770 | Ad-hoc File Transfers | This enhancement allows the transfer of files between users using a quick share link for a given file, which is protected with a password, expiration date, and number of downloads. The links and associated files can be shared with any type of user, including external users as long as the user is provided the password. Each file for which an ad-hoc file transfer link is generated is given a unique ID/token that is used in the associated URL. All ad-hoc file transfer links are generated and managed through the Web Transfer Client. The user must have local auth and admin??(read/write?). LDAP authentication will be incorporated in future releases. A local server in UDMG must be created with the local auth protocol attached. Best Practices: ?? share the link and password via different methods; store in different locations? Web Transfer Client pull in screenshot of page + fields +steps to create –
For all generated ad-hoc file transfer links, the following actions are available.
Note: A revoked ad-hoc file transfer link cannot be restored. A new link must be generated for the associated file and parameters. UDMG Admin UI From UDMG Admin UI navigation pane, select Ad-Hoc Activity to view the list of ad-hoc file transfer links generated and associated details. The ad-hoc file transfer links cannot be edited via the UDMG Admin UI. The Ad-Hoc Activity Details include:
New endpoints added:
| ||
B-18765 | Delete file after download from SFTP (MOVE Command) | This enhancement allows the deletion of a file after it is downloaded from SFTP using the MOVE command. The enhancement only applies to send or receive files. The change removes the need for additional configuration and monitoring in UAC and UDMG. Before this change, the local file could only be deleted in the UDMG Server with the DELETE post-task. The remote file could not be deleted in UDMG and UAC was required for the transfers where remote delete was required.
Examples:
Implemented Error Messages:
|
...
Backlog | Title | Description | ||
---|---|---|---|---|
B-19917 | Updates to Secure JWT Token | This enhancement improves the security between UDMG Admin UI and UDMG Authentication Proxy with the use of session ID instead of user credentials after the initial login (secured the JWT token). Before this change, the user credentials were stored in the JWT payload, which exposed it to potential unauthorized access. The password was removed from the JWT Token and now the header 'X-Session-Id' must be included in each request. | ||
B-19918, | Security Hardening | Improves security with a default NGINX configuration including the recommended security HTTP headers, hiding the server version, and disabling weak TLS ciphers. no impact; when installing the new Note: When installing UDMG 2.0 version a new configuration file is generated with "new" added at end file; no action/fyiend.
|
User Experience
Backlog | Title | Description | ||
---|---|---|---|---|
User Interface Updates | Need to specify what pages/web This enhancement improves This enhancement improves the usability of the UDMG Admin UI and Web Transfer Client, allowing for improved viewing of easier access to information, customizations, searching/filtering, and new features. Aligns look and feel and features The changes align closer to UAC. DATA Dump per Demo – some might be not be things we want to document/highlight Universal Data Mover Gateway Admin UI ChangesKey Changes Include: HAVENT FINISHED UPDATES for this one Left Navigation Pane (idk what we call this throughout)Landing Page / Homepage
Transfers
Left Sidebar Menu - Rules tab
License
Ad-hoc Activity asdfasdf Shared Accounts
Left Sidebar Menu - Licensing
Left Sidebar Menu - Rules
Cluster Nodes
left nav pane - ad hoc file transfer | |||
B-18766 | Added Server State Status and Information in Details | This enhancement allows the user to quickly view the server status, including server state and information in the Details tab Local Servers list for all local servers. The "Status" column was added to the list of local server details. Before this change, the local server status details were only displayed in the “UDMG Server Status” popup. status column within the local servers from nav pane is new; prior you clicked the bottom thing and onlyhad pop up The color-coded bars show the internal service status:
**is service right here or server? | ||
B-19796 | SSH Key Parsing Tool | This enhancement provides a tool to parse a an SSH public key. The UDMG Server only accepts the OpenSSH format for public keys, so customers who use the PKCS8 and DER format were not previously able to convert keys to OpenSSH using standard tools (openssl and ssh-keygen). Authorized key (OpenSSH) PEM encoded formats (PKCS8, PKCS1) The tool parses a SSH public key and shows the following details:
Supported formats are: The supported input formats are:
The output of the tool shows the key details and the OpenSSH format that is suitable for use during the setup of SFTP servers on UDMG:
Command line usage:
See Utilities Reference Guide: udmg-sshkey for additional details. |
Architecture
Backlog | Title | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
B-18759 | Allowing the Sharing of Accounts Between Servers | This enhancement allows the sharing of accounts between servers. It avoids the need for duplicate configuration for FTP and SFTP local servers by having accounts that are shared between local server. (another option would be to allow a server to support multiple protocols)-???? Prior to this change, a local account was only defined for a given local server and it was not possible to have the same account for multiple protocols. For instance, to allow a partner to transfer files over SFTP and FTP, it was required to have both an SFTP and FTP server, each with its own account. Each account was then maintained independently which created additional overhead in configuration and maintenance (password or key updates). The implementation uses the current Local Account table and a New table for handling authorization. Be able to list share accounts from server endpoint.
New command line:
Both the new and old command line can be used to add a new shared account.
Usage:
Prior to this change, in order to create a local account, the user had to create a local server on the Local Server tab first and then create a local account within the XX tab. The user could then edit the local account from the Local Account tab. **A local account could not be created from the Local Account tab directly. The enhancement changes the local account creation process. The user must create the local account from the Shared Accounts tab and does not require the local server to be created yet.
add info about disable | ||||||||||
B-18755 | License Control | This change incorporates license management within Universal Data Mover Gateway. All instances of Universal Data Mover Gateway are now required to have a license key attached to the installation. Universal Data Mover Gateway is licensed by the number of executions per month*; specifically, the number of file transfer instances that completed as DONE over a period of one month. is there any distinction in the transfer types? like all count or only incoming vs outgoing? To receive and apply your license keys, please follow the below steps and reference UDMG Licensing.
| ||||||||||
B-18762 | Using Same Virtual Folder Name for Multiple User Accounts | This enhancement allows a customer to use the same virtual folder name for multiple user accounts. Multiple accounts can now use the same local server and the same vpath, but each account will point to a separate ("private") local directory. make sure the local directory has the privilege to post read/write by the udmg user
Placeholders are allowed in the transfer rule paths (local directory and temp directory): They are expanded at runtime (when transfer is starting or when a FTP/SFTP command is executed). example udmg-client rule add -n Rule10 -d receive -p /data-host --local-dir '/data/#REQUESTEDHOST#' |
...