Signiant Support

13.0 Signiant Manager and Agents Release Notes Print

Release Notes

This document details a summary of the Release Notes for the current release (13.0).

If you are upgrading from prior releases, you should obtain the release notes for those versions to learn more about the features and issues in those releases.


Supported Upgrade Path

Signiant supports the following upgrade paths:

  • 11.0 and higher  to 13.0

If you are running a release prior to 11.0 please contact support for the upgrade path. If you are upgrading from a release prior to version 12.1, you should read the release notes for the interim releases (e.g. 11.0) prior to performing this upgrade.

IMPORTANT UPGRADE NOTE: Before performing any Manager upgrades, you must ensure you have twice the disk space available as currently required by the Postgres "data" directory. The "data" directory is located under ../dds/db/pgsql/ (Linux Managers) and \signiant\mobilize\db\pgsql (Windows Managers).

NOTE: For Mac upgrades, read Mac Agent Upgrade.

Supported Operating System Updates

NOTE: Manager and Agents 12.0 is the last major release to include Agent support for Mac OS X 10.7 and 10.8

Security: Managing SSL

To improve Signiant Manager security, only TLS 1.1 and above are supported for Signiant web server communication. Signiant Agents use the highest level of supported TLS to optimum security and communication. If you want to run a Signiant Manager with an SSL protocol lower than TLS 1.1, use

If you're using Internet Explorer 9 or 10 and want to enable TLS 1.1 or TLS 1.2, do the following:

  1. In the Tools menu, select Internet Options.
  2. On the Advanced tab, enable Use TLS 1.1 and Use TLS 1.2. You can optionally disable Use SSL 3.0.
  3. Click OK.

Note: to enable SSL V3, your Signiant Manager and Agents must be running version 11.4 or higher.

Because SSL V3 is disabled on your Signiant Manager and if you have written Perl scripts that use the Net::SSL Perl module for HTTPS communication, you must modify your Perl script to use IO::Socket::SSL module.

If you have the following line in your Perl script: use Net::SSL, do the following:

  1. Remove use Net::SSL.
  2. Insert the following:
    if (eval {require IO::Socket::SSL;1})
         IO::Socket::SSL::set_defaults(SSL_verify_mode => SSL_VERIFY_NONE);
         require Net::SSL;

If the SSL verify mode needs to verify the server certificate, insert the following:

if (eval {require IO::Socket::SSL;1})
     my $caCertString = '<PEM encoded CA certificate string>';     
     require IO::Socket::SSL::Utils;
     my $caCertHandle = PEM_string2cert($caCertString);
                 SSL_verify_mode => SSL_VERIFY_PEER,
                 SSL_ca => [$caCertHandle]
     require Net::SSL;

With these changes, your Perl script will work without any further modifications.

Mac Agent Upgrade

When you're upgrading to 13.0 from pre-12.0, upgrade-in-place cannot be used. If you're upgrading from 12.0 or 12.1, upgrade-in-place is supported.

To complete an initial upgrade to 13.0 on Mac Agents, do the following:

  1. In the Agent Installation User's Guide, follow the installation instructions in Installing the Agent on MAC-Based Systems (Chapter 2 Installing).
  2. In the Agent Installation User's Guide, follow the upgrading instructions in Upgrading on Mac (Chapter 3 Upgrading).

After manually installing and upgrading to 13.0 on Mac Agents, you can use the upgrade-in-place procedure to upgrade to subsequent 13.x versions.

Signiant Agent Upgrade on Red Hat 7 and CentOS 7

In 12.1 and previous releases, RedHat 7 and CentOS 7 agents used binaries built for the RedHat
6/CentOS 6 distributions. When using upgrade-in-place on such agents the agent bundle is upgraded
to version 13.0 of the Signiant Agent, but will continue to use binaries built for RedHat 6/CentOS 6.

To use binaries built for RedHat 7/CentOS 7 you need to manually upgrade the agent software using
the installer bundle specifically built for RedHat 7/CentOS 7, see the Agent Installation User’s Guide,
and follow the installation instructions in Upgrading on Unix/Linux.

Core Upgrade Considerations

The following section details core upgrade considerations.

Linux Shared Memory Size

Before installing or upgrading on Linux, make sure the maximum shared memory size is set to a minimum of 512 MB. If it is not, the database on the Manager will not start.

Type the following:

cat /proc/sys/kernel/shmmax

If the value is greater than 536870912 (512 MB), you do not need to do anything, and may proceed with the installation. If it is less than 536870912 (512 MB), make sure you do the following:

  1. Add the following to /etc/sysctl.conf:kernel.shmmax = 536870912

    This ensures that the change in the shared memory size will persist across server restarts. You need to reboot for this change to take effect. However, if you do not want to reboot at this time, you can follow step 2 to change the shared memory size during the current runtime.

  2. Type the following:

    echo 536870912 > /proc/sys/kernel/shmmax

Media Exchange Upgrade Considerations

No specific upgrade considerations are required for this release.

Browser Plug-In Support with the Media Exchange Java Applet

Note: This applies only if you're using Java. For information about the Signiant Transfer API, contact your account representative.

In order to use Media Exchange, you must permanently activate Java in your browser. Refer to the instructions below for each browser.

Mozilla Firefox

To activate Java, do the following:

  1. In your Mozilla Firefox browser, click the red plugin icon in the address bar.
  2. In the message window that opens, from the Activate All Plugins drop-down menu, select Always activate plugins for this site.

Apple Safari

To activate Java, do the following:

  1. From the Safari menu, select Preferences and click the Security tab. Ensure Allow Plug-ins is enabled and then click Manager Website Settings.
  2. The Manage Website Settings panel displays the available plug-ins. Select Java and on the right, your Media Exchange website is displayed.
  3. Right-click your Media Exchange website and select Allow and Run in Unsafe Mode.
  4. When prompted, click Trust.

Internet Explorer

To activate Java, do the following:

  1. When you are prompted to run the application, enable Do not show this again for apps from the publisher and location above.
  2. Click Run.
  3. On the Security Warning message asking you to allow access, enable Do not show this again for this app and web site.
  4. Click Allow.

New Features

This section describes the new features associated with this release of the software.

Object Mover

New for our 13.0 release is workflow support for your on-premise object storage. Using the Object Mover workflow and applications you can easily manage transfers into and out of your on-premise object storage. Object Mover is comprised of the following applications:

  • ObjectDropBox: Transfers data between a single source location and one or more on-premise object storage locations. It polls the specified location at a user-determined interval and sends any changes detected in the source location to the specified destination locations.
  • ObjectUploader: Retrieves files from multiple agents to a single target agent, and stores the files on the designated on-premise object storage. The files transferred from the source agents may be stored on a per agent basis, or in a single flat folder on the target storage server. This is referred to as a pull file transfer template.
  • ObjectDownloader: Retrieves files from your on-premise object storage servers and transfers these files to your local or network attached storage.These transfers can be scheduled, encrypted and managed from within the Signiant Manager UI.
  • ObjectReplicator: A bulk file transfer solution that allows you to schedule a distribution from a source on-premise object storage server to one or more on-premise object storage servers (with an option to synchronize the target with the source).
Object Mover is supported on the following platforms:
  • Mac OSX 10.10 and higher
  • RedHat Linux 7, CentOS 7 and higher
When using Object Mover on RedHat 7/CentOS 7 agents, the agent must use binaries built for
RedHat 7. See the Agent Installation User's Guide, Chapter 3: Signiant Agent Upgrade on RedHat 7
and CentOS 7

Dashboard Widget Updates

In this release we've added the following dashboard widgets:

  • Transfer Volume: displays an overview of the transfer activity for selected Agents.
  • Agent Bandwidth Usage: displays the bandwidth for the selected agent.
  • Bandwidth Utilization: allows you to view bandwidth utilization for all transfers that are currently running on all of the listed Agents or on a specific Agent.
  • Transfers Graph: allows you to view the total number of files transferred, total amount of data transferred, and the bandwidth used.
  • File View: allows you to search for a specific file and view all applicable transfer details
  • Zoomable Agent Status: allows you to zoom in on a specific location to see agent status details.

We updated the System Overview widget to provide more customization and a better indicator of the data being displayed.

Agent File Systems

For 13.0 we have added support for de-duplicated file systems on Windows Agents. Previously, Agents did not find and transfer files and folders within Windows de-duplicated file systems.


In this release, we have made the following security improvements:

  • Updates to various libraries and the JDK.
  • Now, to download the sigsetup.inf file, administrators must be authenticated.
  • Data transfer and request security has been enhanced.
  • New user permissions have been updated to further Signiant Manager security.
  • When transfers are initiated by a version 13.0 agent, security handshakes will negotiate to the highest common TLS version supported by both agents. SSL v3 and lower are no longer supported.
  • Openssl has been updated to 1.0.2j.


We've made the following enhancements:

  • The Active Filename column has been added to the Statistic table. This column displays the name of the file being transferred when the page is refreshed.
  • A number of Health Check updates have been made including: option to monitor JVM memory status/usage, option to list all Agent tunnel details, and to show the status of maintenance, certificate, and backup jobs.
  • Copy and paste functionality has been added to components on the Workflow canvas.
  • A new Timeout option has been added to Directory Services to allow you to configure the read timeout value for the directory server.
  • Administrators can now browse the file and folder structure of local agents.

Browser and Platform Support Changes

Added Manager and Media Exchange GUI browser support for:

  • Mozilla Firefox 47 - 50
  • Apple Safari 10, 10.0.1
  • Microsoft Edge 14

To use the Signiant App for Interactive Transfers the following browsers are recommended:

  • Internet Explorer 11
  • Google Chrome (Latest version)
  • Microsoft Edge (Latest version)
  • Mozilla Firefox (Latest version)
  • Apple Safari 7, 8, 9.0.3, 9.1, 10, 10.0.1
  • Microsoft Edge (HTML 12, 13)

Windows Server 2016 (64-bit) support has been added for Signiant Manager, Media Exchange Web Server, Signiant Agent, and Media Exchange Server.

Support for TAPI 2.6 has been added.


This section contains information about limitations with the product.

System Port Range Changes for Windows

In order for the Signiant Manager and Agent software to run on Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista , you must make a configuration change to the system port range. In most cases, there will be no adverse effects to making this change, so you can choose to have the Signiant installer make the change for you.

To comply with Internet Assigned Numbers Authority (IANA) recommendations, Microsoft has increased the dynamic client port range for outgoing connections in Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista. The new default start port is 49152, and the default end port is 65535. This is a change from the configuration of earlier versions of Microsoft Windows that used a default port range of 1025 through 5000.

A full description of this change is available at: and

What Change is Required?

The dynamic client port range should be changed to 49500-65535 in order to avoid potential conflicts with the Signiant software, which uses some TCP and UDP ports within the system default port range.

Instructions for Making this Change Manually

If you choose not to let the Signiant installer make this change for you, use the following netsh commands to set the dynamic port range to the Signiant-recommended values on a computer that is running Windows Vista or Windows Server 2008:

  • netsh int ipv4 set dynamicport tcp start=49500 num=16036
  • netsh int ipv4 set dynamicport udp start=49500 num=16036
  • netsh int ipv6 set dynamicport tcp start=49500 num=16036
  • netsh int ipv4 set dynamicport udp start=49500 num=16036

You can view the dynamic port range on a computer that is running Windows Vista or Windows Server 2008 by using the following netsh commands:

  • netsh int ipv4 show dynamicport tcp
  • netsh int ipv4 show dynamicport udp
  • netsh int ipv6 show dynamicport tcp
  • netsh int ipv6 show dynamicport udp

Anomalies Fixed

This section describes previous known anomalies that were fixed in this release.

General Anomalies

PR Description
PR-23065 When the location (agent/group) for a portal is incorrectly configured, the portal list fails.
PR-24836 The JBoss log is displaying the following message multiple times: Exception occurred authentication user: null.
PR-24855 The display of the transfer rate in the Job List/Job View is failing after transfers.
PR-25529 An incorrect HTTP response code is returned by a FIMS SOAP failed cancel.
PR-25917 The Schedule Jobs permission allows the deletion of jobs.
PR-25978 The Mac OSX Agent installer does not allow custom mode (full prompt).
PR-26002 There is an issue with the CA passphrase special characters.
PR-26003 The upgrade fails when trying to add System to the DTM Group.
PR-26019 Organization administrators cannot edit the passwords for users in their organization.
PR-26033 A manual refresh of the Dashboard causes the Map widget to expand.
PR-26034 Media Exchange emails are not being sent after upgrading to version 11.4LA11.
PR-26042 The Job fails when the Job Template Library name is long.
PR-26055 After an upgrade, Job details read as "unavailable" for templates.
PR-26063 The Signiant Manger Health Check CPU count and core count are incorrect.
PR-26066 The Health Check agent time check needs to be cleaned up.
PR-26071 The response time when saving and loading the Workflow canvas needs to be improved.
PR-26088 The Mail Server connection timeout value in the Email Notification isn't being used.
PR-26132 FIMS is displaying an incorrect failure response.
PR-26142 The Job Details transfer rate graph is not displaying the time axis properly.
PR-26151 The Signiant Manager returns an invalid password when the CA is not running.
PR-26160 The version number in the Agent table is not updated after completing a Media Exchange web server upgrade.
PR-26161 The FIMS documentation does not include the required internal values for Flight prompts.
PR-26163 There are Flight Workflow File List component-related failures.
PR-26166 Health Check is showing the same backup/maintenance jobs multiple times.
PR-26185 The Signiant Flight Report shows the incorrect date for Flight delivery log entries.
PR-26208 No usable information is included in a failure notification.
PR-26229 When the Media Exchange user list is long, it takes over 30 seconds to retrieve the Media Exchange transfer profiles.
PR-26235 The Root Certificate page allows multiple imports with the same identifier.
PR-26260 In Media Exchange 12.1, packages are not available after editing.
PR-26262 The following error is displayed when publishing a template: children[i].children is undefined.

Known Anomalies

This section lists known anomalies and any workarounds that may be available.