MFT Server Release Notes - Version 2024
The release notes for version 2024 include the 2024.1 scheduled release and all its associated patches to date.
To access the patch information, click on the desired link below.
| Release Date | Version Number |
|---|---|
| March 12, 2024 | Version 2024.1.1 |
| March 14, 2024 | Version 2024.1.2 |
| March 29, 2024 | Version 2024.1.3 |
| April 30, 2024 | Version 2024.1.4 |
|
May 9, 2024 |
Scheduled Release 2024.1 - February 2024
Enhancements
MFT-696 - Added support for connecting to Azure storage using managed identity.
MFT-689 - Added a new Trading Partner named Tidal and an accompanying Trigger Action named Run Tidal Process.
MFT-927 - Documented the steps on how to access AWS S3 buckets from a K8 Cluster using the IAM role feature.
MFT-1220 - Enhanced the navigation experience when adding and modifying Triggers. The trigger wizard that required you step through each configuration option using Next and Back buttons has been replaced with tabs that allow you to access an option (i.e. Parameters, Conditions, Actions) directly.
MFT-1254 - Improved the MFT Server Windows upgrade process to prevent the database schema from being updated twice when upgrading in a clustered environment.
MFT-1255 - Added the ability to search the Domains module on various fields using the familiar SQL Like search functionality.
MFT-1327 - Implemented Redwood portal integration.
MFT-1369 - Added a new variable named TradingPartner to Directory Monitor related Trigger events. The variable has a value when a Trading Partner is mapped to the Directory Monitor.
MFT-1434 - Added support for additional special characters to be allowed in the Name field when creating an MFT Server Administrator.
MFT-1436 - Added a Support Admin user to JSCAPE SaaS environments allowing Redwood Support access to log files when necessary.
MFT-1447 - Added ClamAV antivirus scanning out-of-the-box for JSCAPE SaaS environments.
MFT-1465 - Modified what IP address is blocked when reaching the password failure limit for a client setup on an AWS EC2 instance behind an Application Load Balancer (ALB).
MFT-1472 - Improved performance when files are uploaded using HTTP/S protocols.
MFT-1474 - Added the ability to restart MFT Server via a UI button added in the Status > Server module.
MFT-1523 - All PGP Trigger Actions have a new field - “Fail if key is expired’. The target action will fail when this field is enabled and the encryption/signing key is expired.
MFT-1525 - Added a feature where, when a new user tries to log in to MFT Server using OpenID Connect SSO, the system will search in non-standard SSO response fields for a readable username to use when creating the new user account in MFT Server.
MFT-1562 - Added a new Enable Management service checkbox in Settings > MANAGER SERVICE > Manager Service > Manager Service tab.
MFT-1654 - The SFTP/SCP Service Algorithms dialog has been redesigned in the Global Services/Domain Services modules to ensure readability and to allow for filtering.
MFT-1713 - When accessing documentation from the JSCAPE website, there is now a version picker located on MFT Server's landing (Overview) page.
Patches (released after 2023.3 and included in 2024.1)
Version 2023.3.1 - Released December 19, 2023
MFT-1427 - In the Domain > SECURITY > Banned Files module, the search feature is not allowing you to enter a value for the default search field (Path), or change the search field to another option in the dropdown list.
MFT-1429 - In the Domain > SECURITY > DLP Rules module, the search feature behaves incorrectly when checking the Field checkbox. The screen continuously blinks and displays a message “Processing, please wait”.
MFT-1437 - In the Domain > SECURITY > IP Access module, when searching on the Access field with a denied value, the value flips from denied to allowed when the search icon is clicked.
MFT-1363 - JSCAPE SaaS –Single Sign On (SSO) issue – encountering a redirect URI mismatch error.
MFT-1441 - When adding a key with special characters, then subsequently viewing it in the Key Details dialog, the key title doesn't match what was entered.
MFT-1444 - Error when attempting to send an adhoc email - java.lang.NullPointerException - Cannot read the array length because "array" is null.
MFT-1103 - The status code when a quota is exceeded has been changed to SSH_FX_QUOTA_EXCEEDED (15).
MFT-1439 - Web UI login with Captcha enabled results in a 500 error.
MFT-1340 - In certain scenarios, when the Ad-Hoc Activity grid contains no records, all four of the action buttons (e.g. Copy, View, etc.) are enabled when they should be disabled.
MFT-1448 - Health Service data uploads intermittently contain no data.
MFT-1449 - When banned files are specified and a Web Client user attempts to upload a file not allowed, the message they receive is incorrect ("Files uploaded successfully").
Version. 2023.3.2 - Released February 13, 2024
MFT-1508 - Unable to expand the column in the Domains grid which makes reading long domain names problematic.
MFT-1542 - Unable to access the non-admin UI in a JSCAPE SaaS environment.
MFT-1524 - When an SFTP Service is configured with “Password or Public Key” as the authentication type, and the connecting user’s password has expired and they are only using the public key to connect, prompt the user to set a new password.
MFT-1555 - Improved the Health Service statistical data that is sent to AWS.
MFT-1597 - For all export operations, changed the default file extension from '.log' to '.txt'.
MFT-1551 - In certain scenarios, the Trading Partner Synchronization Trigger action fails with a java.io.EOFException.
MFT-1292 - Implemented a Redwood Portal connection framework for customer SaaS accounts.
MFT-1608 - Encountering a 404 error when configuring an RMJ Trading Partner.
MFT-1610 - In a JSCAPE SaaS environment, uploaded/downloaded file details are not displayed for smaller files.
Patch Releases for 2024.1
MFT-1787 - When saving a trigger, the following error occurs: "Internal server error! The parameter is incorrect".
MFT-1821 - FTP download trigger actions will fail when transferring to an FTP server that does not support the MDTM command.
MFT-1858 - LDAP authentication is failing with an error (Authentication Service error. javax.naming.InvalidNameException) when a user attempts to log in.
MFT-1875 - A '500 Internal Server Error - Blob already exists' error occurs in the Web Client UI when attempting to overwrite a file using the Microsoft Azure Blob Service network storage mapped to user storage.
MFT-1874 - A '500 Internal Server Error - Status code 416' error occurs in the Web Client UI when attempting to overwrite a file using the Microsoft Azure File Service network storage mapped to user storage.
MFT-1859 - An error - 'Cannot rename file: I/O error' occurs in the Web Client UI when attempting to rename a file using the Microsoft Azure Blob Service network storage mapped to user storage.
MFT-1881 - Performance issues observed when transferring files.
MFT-1740 - An enhancement was made to the behavior of the existing Directory Monitor > 'Monitor interval' field. If this field is disabled (unchecked), then later re-enabled (checked), any Directory Monitor event type (file add, change, etc.) that occurred during the disabled period will be processed.
MFT-1757 - A new trigger Event type named Directory Monitor File has been implemented. It lets a user specify a trigger condition that includes multiple directory monitor event types (e.g. file add, changed, etc.). Should an event type specified in the condition expression occur, the trigger will execute. Supported event types include: File_Added, File_Changed, File_Deleted, and File_Aged. For example, the user can specify that a directory monitor file add or file change should run the Directory Monitor File trigger. This is accomplished by setting the Directory Monitor File event type with a condition expression as follows: EventType = "File_Added" OR EventType = "File_Changed".
MFT-1881 - Performance issues observed when transferring files (additional improvement made after the prior 1.2 patch release).
MFT-1817 - When using the Web Client UI to upload a large file in a JSCAPE SaaS environment, the status bar continuously states the remaining time to upload is "unknown".
MFT-1824 - Unable to upload a security key for an SFTP trading partner in a JSCAPE SaaS environment.
MFT-1854 - Unable to connect to SharePoint network storage.
MFT-1923 - The user list is not displaying correctly in Domain > ACCOUNTS > Groups > Users > "Setup <Group Name> Users" dialog.
MFT-1918 - New fields were added to several Trading Partner actions.
Reading Buffer Size - This is the amount of data (KB) that can be read in 1 request.
Writing Buffer Size - This is the amount of data (KB) that can be written in 1 request. When the write buffer is full, the system pushes the data to its destination.
As a general rule, the data transfer speed increases as the buffer sizes increase. SFTP can be sensitive to buffer size. Typically 32 KB for both the read and write buffers work the majority of the time. If an SFTP trading partner generates a protocol error due to a buffer limitation, you may need to modify these fields accordingly.
The grid below depicts the name of the Trading Partner actions that were updated with the new field(s). Some were updated to include both the Reading and Writing Buffer Size fields, and some were updated to include only the Writing Buffer Size field.
Trading Partner Action Reading Buffer Size Default Value (KB) Reading Buffer Size Minimum Value (KB) Reading Buffer Size Maximum Value (KB) Writing Buffer Size Default Value (KB) Writing Buffer Size Minimum Value (KB) Writing Buffer Size Maximum Value (KB) Trading Partner File Download 32 1 512 512 1 1024 Trading Partner File Upload N/A N/A N/A 32 1 512 Trading Partner Regex File Upload N/A N/A N/A 32 1 512 Trading Partner Regex File Download 4 1 512 512 1 1024 Trading Partner Copy File 4 1 512 512 1 1024 Trading Partner Copy Regex File 4 1 512 512 1 1024 Trading Partner Move File 4 1 512 512 1 1024
IMPORTANT UPDATE: April 10, 2024. This is applicable to the 2024.1.3 patch (fixed in patch 2024.1.4)
It has been reported that the Trading Partner Regex File Download action, when used with an SFTP trading partner, is creating 0 byte files when the Writing Buffer Size is set to 512 KB and the Reading Buffer Size is set to 4 KB. The trigger action is not failing when this happens, creating a false impression that the download is working successfully.
To address this issue, change both the Reading and Writing Buffer Size fields to 64 KB, as depicted in the image below.
MFT-2005 - The Trading Partner Regex File Download action, when used with an SFTP trading partner, is creating 0 byte files when the Writing Buffer Size is set to 512 KB and the Reading Buffer Size is set to 4 KB. The trigger action is not failing when this happens, creating a false impression that the download is working successfully.
MFT-2043 - Trading Partner Move File action does not fail if the source file is not present, but rather, the trigger status hangs in a running state.
MFT-2036 - Trigger actions running in parallel randomly hang in a running state.
MFT-1911 - When starting 3 or more MFT Server nodes at the roughly the same time, a start up error intermittently occurs as follows: Entry is out of date.
MFT-2069 - The Trading Partner Copy Regex File action, when the Delete on Success field is checked, is not deleting the file when the Advanced > Threads field is greater than 1.
MFT-2080 - The PGP Decrypt File action is failing with the following error: `java.nio.channels.ClosedChannelException`
MFT-1953 - The js-ipaccess.exe command-line command is failing with the following error: Error Message: `com.jscape.inet.mftserver.adapter.management.b: Code: INTERNAL_SERVER_ERROR; description: Error obtaining access rules for domain 'a'.; details: com.jscape.inet.mftserver.operation.J: java.lang.NullPointerException`.
MFT-1888 - When Importing a PGP public key that includes a comma in the key file name, the following error occurs: File corrupted or has unsupported format. Invalid key name.
MFT-1813 - Optimized file transfer operations for SMB load balancer Trading Partner and Network Storage types, which returned the error "Different server found for same hostname [hostname]”.
MFT-1684 - A new Host/Public Keys column was added to the SFTP/SCP Algorithms window. This allows you to enable and disable host keys on both the global and domain level.
General enhancement
Added a Threads field to several existing trigger actions (e.g. FTPS Regex File Download). The Threads field controls how many files are transferred in parallel. The minimum value is 1, and the maximum value is 99. Its purpose is to increase the speed of file transfers as the number of threads are increased. This field may require some testing to determine the most favorable results. Be aware that setting the number too high may result in network overload.
MFT - 2142 - MFT Server cannot access an AWS S3 "folder" if the S3 object for the folder does not exist.
MFT - 2103 - Unable to obtain a directory listing when using a SharePoint trading partner with Delegated Permissions.
MFT - 2003 - SMB trading partner is unable to connect to an Amazon FSx server when MFT Gateway has a delegated TCP-TCP reverse proxy configured to point to the FSx server.
MFT - 2138 - An SFTP trading partner configured with the ssh-ed25519 public key algorithm is failing with the following error when attempting to connect: com.jscape.filetransfer.FileTransferAuthentication.Exception.