03-April-2025 Ver 6.6.1

Release Notes - [Thru AFT] [Ver 6.6.1.30]

Release Date: [03-April-2025]

We have a short video that goes over the new features and functions.

[New Features]

Azure Files Endpoint

A new endpoint type has been introduced, enabling Thru to directly pull from or push to Azure Files.

The configuration process mirrors that of the Azure Blob Endpoint type. It supports three authentication methods: Shared Access Token, Connection String, and Access Key.

Node Direct is not available for this endpoint type yet.

Reports

A new button, titled “Export,” has been introduced on the Activity Page.

Clicking the “Export” button will generate a .CSV file containing the results of the activity page, based on the filters you have selected.

The report generation process begins once you click the button. If you leave, log out, or return later, you will be able to download it from the new reports page.

SSO Mapping

Administrators now have enhanced control over SSO user creation. They can set up SSO mappings that automatically pull attributes from their IDP and assign specific roles and permissions during onboarding. This streamlines user management and ensures a more flexible, automated approach to handling SSO access.

The new "SSO Mapping" section within the Admin interface empowers customers to automatically assign roles and organizational associations based on specific traits identified in Single Sign-On (SSO).

[Improvements]

Thru Node Alerts

Node email alerts now offer three configuration modes

New Node Alert Configuration Options:

• Alerts Disabled: If alerts are turned off, you won't receive any alert emails, though UI alerts will still appear.

• Default Email Alerts: When alerts are enabled without specifying an email list, all instance admins will automatically receive alert emails.

• Custom Email Alerts: If you enable alerts and provide an email list, only those specified addresses will receive the alert emails.

Users have the ability to easily transfer lists of email addresses from one node to another, facilitating the configuration of email lists across multiple nodes.

Customer Instance Code

The current customer instance code is now shown next to the User Profile

[Bug Fixes]

[Activity] - Organization users may see sources or targets that are not intended to be visible to them.

[Endpoints] - View associated flows modal window formatting updated.

[Flows] - Subscribers corrected a spelling mistake.

[Flows] - Users with Organization associations see unexpected Flow Endpoints.

[Internal SFTP] - Fixed issues with virtual paths, some SSH_FXP_OPEN commands were adding double-slashes to the beginning of a file path.

[MOTD] - Back end fix to resolve issue with Thru’s Message of the day function.

[Node] - The Thru Node heartbeat alert e-mail has inconsistent time stamps.

[Processing] - Batch Decompression using Zip would not work if folders were included.

[Processing] - PGP decryption failing.

[Rename] - Cancel Button on Rename tab stopped working.

[Transfer Manager] - Client Error messages too long.

[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.