Universal Data Mover Gateway 1.5.0 Release Notes

If the remote filename stub in the transfer request starts with a '/' it is considered an absolute path and will be used without prefixing with the transfer rule remote directory path. 

For example, the client transfer udmg-client transfer add -f localFile.txt -o /remotepath/remoteFile.txt -p SftpPartner -l remoteAccount -w send -r Rule1S will now send /remotepath/remoteFile.txt as the path in the SFTP request whereas before, the path would have been {rule remote_directory}/other/remoteFile.txt.

The open sessions for the users of the UDMG Admin UI can be displayed and terminated from the user menu.
Requires the 'administration write' permissions.

• Ability to manage the 'Administration' permission from UI and CLI

• 'superuser' shortcut is provided to create or convert a user to a superuser with all possible permissions, including the administration permissions
  

  udmg-client user update bob -r 'superuser' 

Ability to globally disable each rule task type.

New udmg-server configuration parameters, in the [tasks] section, for each task type allow to disable the related task processing during any file transfer. For the following task types: COPY, COPYRENAME, MOVE, MOVERENAME, DELETE, RENAME, EXEC, EXECMOVE, EXECOUTPUT, TRANSFER, CHECKREGEX, PUBLISHEVENT, ICAP. 

Customizable banner and system identifier on UDMG Admin UI,

• "udmg.system_identifier": name of the system or the environment.
• "udmg.banner.background_color": color of the banner background, as HTML color name ("Brown"), RGB code ("rgb(165,42,42)"), or hexadecimal code ("#A52A2A").
• "udmg.banner.logo": company logo, optional picture to display next to the system identifier.

Example of a production environment with a brown banner and a development environment with an orange banner:

Improved the usability of Business Service : they can be used for tagging objects and not only to enforce security permissions. A Business Service without any User Group can be attached to an object as a way labeling it.

New debug log messages:

• TRANSFER: Programmed new transfer n°ID of file FILE, from/to PARTNER as ACCOUNT using rule RULE
• COPY: Copied file FILEPATH to FILEPATH
• COPYRENAME: Copied file FILEPATH to FILEPATH
• DELETE: Deleted file FILEPATH
• EXEC: Done executing command PATH ARGUMENTS
  and command output is sent to DEBUG log
• EXECMOVE: Done executing command PATH ARGUMENTS
  and new file path is sent to DEBUG log
• EXECOUTPUT: Done executing command PATH ARGUMENTS
  and command output is send to DEBUG log
• MOVE: Moved file FILEPATH to FILEPATH
• MOVERENAME: Moved file FILEPATH to FILEPATH
• RENAME: Changed target file to FILEPATH

#34215,

#34116

• Change order of the items in the Management and Administration menus, for logical grouping of entities.

   

• Change the order of the options in the User Menu, logout is the now the last option.

Change label for rule parameter: "Path Directory" to "Virtual Path Directory"

Change the references to "Certificate" to "Certificate / Key" depending on the context.

Support for cluster awareness where multiple udmg-server instances are coordinating to have 1 active instance and the remaining ones remain in passive state. Continuous monitoring is performed to ensure that a passive instance will takeover in case of failure or shutdown of the active instance.

The MFT servers are owned by the active instance, which also manage the transfer requests in client mode.

See High Availability Behavior and Processing

• Service description is prefixed with "Stonebranch" for parity with Universal Agent ubroker service.
• Syslog messages are labeled with the service name (udmg-server, udmg-auth-proxy, ...) instead of 'sh'.
• Syslog messages are sent to 'local0' utility for easier filtering.

• Existing /api/sb_healthcheck is enhanced with additional information: node details and node status. 
  Requires authentication but no specific permissions.
  Example of output for a passive instance:
  
  {

      "status": "operational",

      "nodeId": "gateway_1:8080-mft-gw-0",

      "nodeHostname": "gateway_1",

      "nodeIPAddress": "172.99.0.101",

      "nodePort": "8080",

      "nodeStatus": "PASSIVE",

      "nodeUptime": "15h6m4.810854748s",

      "nodeLastUpdate": "2023-11-14T08:07:54.848374Z",

      "nodeLastActiveDate": "2023-11-13T16:57:57.026091Z"

  }
• New /ping endpoint returns the plain text status: 'ACTIVE', 'PASSIVE', or 'OFFLINE' and also the 403 (Forbidden) HTTP code when the node is not active. This API is provided without authentication for load balancers.
• New /api/sb_mgmt_nodes endpoint returns the list of the instances with their details and status.
  Requires the 'administration read' permission.

New Web Services:

• /api/sb_users/{user}/tokens
  • GET to fetch the list of token: User read.
  • POST to create a token: User write.

• /api/sb_users/{user}/tokens/{token}
  • GET to read a given token: User read.
  • DELETE to remove a given token: User delete.

New CLI commands:

Usage:
  udmg-client [CONNECTION-OPTIONS] token personal [username] <command>

[personal command arguments]
  username:           The user's name

Available commands:
  add        Add a new personal access token to a user
  delete     Delete a personal access token
  get        Retrieve a personal access token
  list       List personal access tokens for a user

Note that a token owner is always allowed to manage its own tokens.

New web service and CLI command for a user to fetch its own user profile with system permissions.

GET /api/user_profile

• the output is the same as GET /api/sb_users/{user} for the calling user
• no permission is required