Hotfix TIB_mftccis_8.3.0_HF-001 can be downloaded from TIBCO Support Portal (https://support.tibco.com).  

You will need to provide your TIBCO Support Portal credentials.  Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option. Then go to “/AvailableDownloads/MFT/CommandCenter-InternetServer/8.3.0/” to download the hotfix.

The .zip file has the Readme file inside. Please unzip the file and review the Readme file for instructions on how to apply the hotfix.

Introduction

Hotfixes are cumulative. This is the first hotfix for TIBCO Managed File
Transfer (MFT) Command Center 8.3.0 and TIBCO Managed File Transfer (MFT)
Internet Server 8.3.0.

================================================================================
Closed Issues in 8.3.0_HF-001 (This Release)

MFCC-5562
Apache Struts was upgraded to version 2.5.22.

MFCC-5557
When a string was passed to Window.setTimeout, it issued a
JavaScript eval call.
 
MFCC-5556
The javascript eval functions were removed from the transfer and
admin browser clients, and the web.xml file was updated to remove the
content-security-policy "unsafe-eval" value.

MFCC-5555
Users could not be restricted from creating or transferring files with
servers having "Server Type=LOCAL".
Note: A new web.xml parameter was added that allows you to disable the ability
to create or transfer files with servers having "Server Type=LOCAL":
AllowLocalServerDefinition={True|False}  Default is "True"
True:  Allows transfers with existing servers having "Server Type=LOCAL".
False: Does not allow admins to create server definitions with
       "Server Type=LOCAL", and does not allow transfers with
       existing servers having "Server Type=LOCAL".

MFCC-5551
During audit search, when the AS2 MDN Status check box was selected
and the department was defined, the following error message was received:
"Ambiguous column name 'Aux8'"

MFCC-5549
Connections to target SSH Servers using Key Exchange Algorithm
"curve25519-sha256@libssh.org" failed with the error message,
"The host key signature is invalid."

MFCC-5527
BouncyCastle libraries were upgraded to version 1.66.

MFCC-5523
The dashboard page did not indicate that the transfer charts were for
Internet Server transfers only.

MFCC-5516
When a user uploaded a file to an AWS S3 bucket, the bucket owner did not
get rights to the file.

MFCC-5509
When the collector was unable to find the last transfer collected, collection
stopped for that server.
Note: A new parameter (Reset Collection History) has been added to
Manage Servers > Management Options > Platform Server Management Option.
Reset Collection History - This parameter resets the collection history.
It removes the last transfer ID collected from the collector, and collection
resumes from the time the last transfer was collected.

MFCC-5505
REST data was not filtered for invalid characters.

MFCC-5504
When files were uploaded to the backend Azure Data Lake Storage Gen2, warning
messages were displayed in the console:
"org.glassfish.jersey.client.internal.HttpUrlConnector.setOutboundHeaders"

MFCC-5503
When ZLIB compression was used, Platform Server client transfers that were
restarted to the backend Platform Server failed.

MFCC-5501
When a Platform Server initiated a transfer to Internet Server to a target
Platform Server for z/OS with CRC enabled, checkpoint restart failed with the
error message:
"CRC Mismatch - Transfer terminated with error"

MFCC-5500
When server credentials were configured in the server definition, transfers
to target AS2 servers failed with the error message:
"Unknown config property name "uuuuuuuu""

MFCC-5497
When "Server Credentials" were defined for the transfer user, connections
to Azure Storage failed.

MFCC-5490
SSHTools was upgraded to version 1.7.31.

MFCC-5488
Even when an invalid session ID was passed, the "Delete Session" FT REST call
returned success.

MFCC-5474
When a StorageException error message was received for an Azure request,
adequate information about the error was not displayed.

MFCC-5316
The percentage complete displayed during LDAP sync of a single user
was incorrect.

MFCC-5308
When an SCP client closed the connection, MFT was not notified causing
a thread to remain active even after the connection was closed.

MFCC-5121
When Java 11 running in FIPS mode was used, MFT DB Reports received
an exception.

MFCC-3428
When uploads to a target Hadoop server were initiated, TMP files were
created under the logs\trace.
================================================================================