Signiant Support

13.2 Signiant Manager Release Notes Print

Release Notes

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

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


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


Media Shuttle Dropbox Monitor

Media Shuttle Dropbox Monitor integrates Signiant Managers + Agents and Signiant Media Shuttle which provides transfers between Signiant agents to cloud-based Signiant Media Shuttle storage servers. This workflow gives agents the ability to create dropbox style jobs to deliver content to a Media Shuttle share portal.

Log Management

A new maintenance workflow has been added to allow compression and archival of log files and the option to send logs to agents.

Flight Gateway Configuration

All agents with the ability to act as a Flight Gateway Server will have an option displayed in the Object Agent tab when configuring the agent through the manager interface.

Transfer API

Transfers using the API can use object storage. Signiant agents with access to object storage can read or write to object storage when using the Transfer API.

Email Prompt Enhancements

Workflow developers can now restrict email prompts to a single email address or allow multiple email addresses.

Media Mover Enhancements

Media Mover jobs such as Media Dropbox, Media Distributor, and Media Aggregator can now filter files based on the time they have been created, modified, or accessed, allowing users to transfer files within a specific time period, such as files created after a certain date and time, or files modified within a specific time period.

Job View Export and Import

Job views can now be exported and imported between manager accounts.

Transfer Graph Improvements

The Transfer Graph has been enhanced to provide numeric values when bandwidth throttle, ceiling, or floor are modified.

Object Mover Encryption

Object Mover jobs have now include the encryption options introduced in version 13.1

Apache JServe Security Enhancement

A potential vulnerability involving Signiant JBoss Application Service has been fixed.

REST API Enhancements

Signiant's REST API now includes API calls for job management and scheduling. Client programs can create, edit, delete, and schedule operations to run, cancel, suspend, and resume jobs. All SOAP API job management calls are now available via the REST API.

Browser and Platform Support Changes

Added Manager and Media Exchange GUI browser support for:

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

Anomalies Fixed

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

General Anomalies


PR Description
PB-3180 Compress and Archive Logs
PB-3280 Additional Browser Support
PB-3207 Flight Gateway integration with Manager
PB-3206 Media Shuttle integration with Manager
PB-3260 Log Management Notification
PB-3363 Changes to Object Storage logic
PB-3230 Revised CTE restricted scripts to work with the local object agent
PB-3379 Enhances Email Address prompt with an option for multiple email addresses
PB-3391 Support for Safari 10.1.2
PB-3392 Support for Firefox 55
PB-3424 Media Mover option to only transfer files created after a certain date
PB-3423 Allow import/export of Job Views
PB-3436 Set throttle, ceiling, and floor events to include value in transfer graph
PR-26533 Fixes to port 8009 AJP vulnerability
PB-3439 Object Storage tab revisions
PB-3303 Make Flight Gateway option independent from object storage
PR-26053 No ciphers available when "low"encryption selected
REST Corrections to endpoints