Signiant Support

13.1 Signiant Manager Release Notes Print

Release Notes

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

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

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 13.0, you should read the release notes for the interim releases (e.g. 12.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 ensure 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.1 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.1 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.1 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.1 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.

Dashboard Widget Updates

In this release we've added a new widget and made some user improvements to the Dashboard experience:

  • System Health widget: allows you to view the status of the Signiant Manager, use this information to help you anticipate and prevent outages or other problems caused by an overloaded system.
  • Job Completion: has been updated to display the current job transfer rate.
  • Quick Search: use the new Dashboard drop-down menu to quickly search for jobs and transferred files without having to create and run a transfer report or add a new widget.
  • Manual refresh: widgets now include a manual refresh icon allowing you to get immediate status updates.


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

  • The SHA-1 signing algorithm has been replaced by the SHA-256 certificate/request signing algorithm.
  • To provide you with a more versatile user role, you can now create a user that has permissions to start, stop and restart Jobs but who cannot delete or edit Jobs.
  • Visibility of Media Exchange user configuration options has been updated to limit any security violations.
  • Transferred Media Exchange package details have been limited to package recipients and users with the appropriate channel access.


The Signiant Manager REST API now includes REST calls for Jobs and Resource Controls. With this updated version of the REST API, your client programs can manage users, user groups, agent groups, job groups, jobs, channels, and resource controls.

Media Mover

A number of improvements and updates have been made in 13.1 to Media Mover including:

  • We have added an option to skip 0 byte files from a transfer.
  • The source file deletion process after a successful transfer has been improved to ensure a more efficient and faster operation, eliminating lag and delay.
  • Transfer restarts now account for data that was previously transferred, this ensures that the transfer runs as intended without needing to rerun the entire transfer.
  • The encryption options have been updated to: No Encryption (signed), No Encryption (unsigned), or Encryption On.


We've made the following enhancements:

  • To allow you to better understand license details, the Feature Description column has been updated and this information is also available in the Health Check report.
  • To make bandwidth available based on job priority, the Job Priority Bandwidth Allocation option has been added to Resource Control configuration.
  • The Organization Administrator and System Administrator roles have been updated to better delineate permissions and access.
  • Numerous updates have been made to Health Check to improve the layout and display.
  • Alarms have been added to indicate when jobs are in a deadlocked state and when backup jobs are suspended.

Browser and Platform Support Changes

Added Manager and Media Exchange GUI browser support for:

  • Mozilla Firefox 51 - 53
  • Apple Safari 10.0.3, 10.1, 10.1.1
  • Google Chrome 55 - 58

Added Manager platform support for Amazon Linux AMI.

The Agent installation process has been updated to reduce file size and to add more flexible installation options. The Manager installation bundle has been updated to include only the Agent bundles specific to your chosen platform. This update allows you to customize your installation experience to only download and import the Agent bundles that you need. This redesign has allowed us to support more Agent platforms while reducing the overall time, size and resources required during installation.

  • Debian Linux 8.x - 64 bit
  • Macintosh OS X 10.10, 10.11, 10.12 - 64 bit
  • Red Hat Enterprise Linux 6.x/CentOS 6.x - 64 bit
  • Red Hat Enterprise Linux 7.x/CentOS 7.x/Amazon Linux - 64 bit
  • Solaris 10 - 64 bit Intel
  • Ubuntu Linux 17.x - 64 bit
  • Windows 2003 R2/2008 R2/7/2012 R2/8.1/10/2016 - 64 bit


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-21591 Issues displaying Jobs with the same name but belonging to different Job Groups.
PR-23590 Media Exchange packages with a trailing space are not saved correctly.
PR-24195 Support periodic synchronization of the Manager with the Active Directory database.
PR-24197 Media Mover requires an option to ignore 0 byte files.
PR-24509 Add a cancel option to multi-Agent queries.
PR-24559 When a component name starts with a number, the job fails.
PR-24934 Updated the job completion widget to the display the current transfer rate.
PR-24947 The Java client displays INFO messages as WARNING messages.
PR-24967 Some jobs are displaying as 100% completed when they have failed.
PR-25330 Add a Description column to the Licenses screen.
PR-25439 Remove leading and trailing spaces from the restricted grant folder path field.
PR-25498 Replace the SHA-1 algorithm with SHA-256 for certificate signing operations.
PR-25740 Add an option to Media Mover to move source files to new folders after a successful transfer.
PR-25866 Make the File Transfer Report workflow easily accessible to customers.
PR-26058 Jobs that are run with expired CAs, fail.
PR-26073 Non-transferred FIMS files were not reporting as failed.
PR-26085 The stream growing files feature does not support MXF file metadata changes.
PR-26090 The Job Report is missing job run details.
PR-26099 Add a REST version of the SOAP API.
PR-26108 Improve the resource management bandwidth prioritization.
PR-26181 A problem with an SSL connection causes the dds_pc process to stop.
PR-26192 Scheduler improvements are required to better handle burst job submissions.
PR-26201 The siginit_ha status does not properly detect the CentOS version.
PR-26207 More verbose logging is needed when the SSL connection to the web server fails.
PR-26226 The appropriate jobs should be updated when the start component is renamed.
PR-26281 The Agent installer should detect the existing storage server.
PR-26320 Problem during the CTE integration from to the Signiant App.
PR-26294 The dds_fileutil does not delete files with square brackets.
PR-26301 System and organization administrator roles require improvements.
PR-26306 Improve the workflow for scheduled reports.
PR-26310 Add the ability to search all jobs and transferred files from the Dashboard.
PR-26312 Provide detailed information in the FIMS callback error details.
PR-26313 The FIMS callbacks don't include the timestamp.
PR-26315 Improve the OS X install with a read-only DMG.
PR-26270 User permissions have been improved to add start, stop and restart job options.
PR-26329 Updates are required to the Health Check template.
PR-26330 The Directory Service order is not being respected and users cannot log in.
PR-26337 Update Dashboard widgets to support adjustable height.
PR-26342 Provide the option to disable the concurrency setting in a resource control.
PR-26344 The job resource control queue should display interrupted jobs.
PR-26346 The cloud components are missing from the Restrict Component Access list.
PR-26369 Increase the error details in the response callback for non-standard FIMS jobs.
PR-26375 Unlock the ZIP component.
PR-26383 Users should not be able to delete from system Job Groups.
PR-26388 The Manager installer should check for port availability for other services.
PR-26391 Add a system health Dashboard widget.
PR-26392 User names with special characters are not authenticated correctly against Active Directory.
PR-26395 Add functionality to sort the Agent relay rules in the GUI.
PR-26397 When there is more than one page of queued jobs against a resource control causes a JavaScript error.
PR-26398 A JavaScript error is returned when updating the Agent location.
PR-26400 Dashboard widgets now support manual refresh.
PR-26411 When large numbers of files are transferred, the Log File Name functionality is causing a delay.
PR-26415 Improve the backup job to enable specification of multiple Agents.
PR-26416 Alert created to indicate deadlocked resource control Jobs.
PR-26417 Add a web services API call to retrieve a filtered list of jobs.
PR-26419 Add a web services API call to query, create, and update resource controls.
PR-26420 The ability to add/edit the All Jobs view.
PR-26421 Update the File Transfer component to not preserve the source path in all instances.
PR-26422 Update the error message for the getJobInfo SOAP method.
PR-26423 Update the Linux Manager install to point to the correct error log.
PR-26424 Add an alarm to alert users when the backup job is suspended.
PR-26427 Add a web services API call to return the job create date/time.
PR-26403 Deletion of Media Mover jobs is slow.
PR-26436 Add the ability to disable the inactivity timeout.
PR-26452 Add Manager & Agent support for Amazon Linux.
PR-26463 The Media Mover target directory path mapping fails during a next day retry.
PR-26465 The file Agent crashes when there are long relay lists associated with long hostnames.
PR-26479 A menu item with a NULL sort order breaks the menu on the administration page.
PR-26480 Publish version 1.1 of the FIMS schema.
PR-26481 The Agent backup workflow is not backing up the Linux configuration file.
PR-26487 Templates pages are slow to load.
PR-26500 Improve the speed of transfers when using encryption.

Known Anomalies

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