27-September-2025 Ver 6.6.5
Release Notes - [Thru AFT] [Ver 6.6.5]
Release Date: [27-September-2025]
This update to the MFT Automated File Transfer application includes a series of security patches, bug fixes, and new feature enhancements. This update strengthens application security through updates to core system libraries and includes fixes to improve the reliability of scheduled transfers and endpoint connections. Additionally, we are introducing new functionality, including expanded authentication options for Azure Blob storage via IDP and greater self-service capabilities for organization administrators.
[New Features]
Azure Blob - External Identity Provider Authentication
Two new authentication options are being introduced for Azure Blob Storage access:
Azure Machine/Client Credentials - Direct communication with Azure and blob storage
External Identity Provider Authentication - Authentication through external providers like Okta or Auth0
For more information see : Azure Blob - External Identity Provider Authentication
External Endpoints - Configurable Concurrent Transfer Support
Implemented a setting which allows a user to define a number of concurrent connections up to a limit.
Note : Number of concurrent files must be between 1 and 5
Note : Thru Node (MFT Runtime) does not currently respect this setting, planned for future node release.
[Improvements]
CSP Security Headers Enabled
CSP Policy - Click jacking prevention
Azure Blob - Added support for Premium ZRS Storage Account type
Note : if required for Node/MFT Runtime contact helpdesk@thruinc.com
[Bug Fixes]
Api Key - Did not respect allowed Orgs, Added logic to the API key handling to prevent org users from stepping outside of their assigned orgs.
Schedules - Weekly Schedules Did not display the day of the week after being saved.
Schedules - Flow Endpoint Schedule Not Running As Configured
[Copyright]
The information in this document is subject to change without notice. This document is intended for the use of Thru Inc. staff, Thru Inc. customers or persons having signed an NDA with Thru Inc. for the purpose of the agreement under which the document has been submitted. No part of this document may be reproduced or transmitted in any form or means without the prior written permission of Thru Inc. The document has been written to be used by professional and properly trained personnel and the reader assumes full responsibility when using it. Thru Inc. welcomes readers’ comments as part of the process of continuous development and improvement of the documentation. Thru Inc. liability for any errors in the document is limited to the documentary correction of errors. Thru Inc. will not be responsible in any event for errors in this document or for any damages, incidental or consequential (including monetary loss), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to applicable laws.