Signiant Support

12.0 Signiant Manager and Agents Release Notes Print




Contents


Release NotesRelease Notes

This document details a summary of the Release Notes for the current release (12.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.


Upgrading

 

 

Supported Upgrade Path

Signiant supports the following upgrade paths:

 

  • 9.0 and higher  to 12.0

 

If you are running a release prior to 9.0 please contact support for the upgrade path. If you are upgrading from a release prior to version 11.4, you should read the release notes for the interim releases (e.g. 10.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).

In 10.4 we added Signiant Manager support for Windows 64bit, for upgrade procedures, refer to the Manager and Agent Upgrade Best Practices. If you need to restore the Manager, follow the restore procedures detailed in the Restore Manager section in the Manager User's Guide.

NOTE: For Mac upgrades, read Mac Agent Upgrade.

Security: Enabling and Disabling SSL V3

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

To improve Signiant Manager security, we have added the capability to enable or disable SSL V3. SSL V3 is disabled by default on new installations. Use the sslEnableDisable.pl script to manage SSL V3 communication.

If SSL V3 is disabled on your Signiant Manager and 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->import();          
         IO::Socket::SSL::set_defaults(SSL_verify_mode => SSL_VERIFY_NONE);
    }
    else
    {
         require Net::SSL;
         Net::SSL->import();
    }
    

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

if (eval {require IO::Socket::SSL;1})
{                       
     IO::Socket::SSL->import();
          
     my $caCertString = '';     
     require IO::Socket::SSL::Utils;
     IO::Socket::SSL::Utils->import('PEM_string2cert');
     my $caCertHandle = PEM_string2cert($caCertString);
     IO::Socket::SSL::set_defaults(
                 SSL_verify_mode => SSL_VERIFY_PEER,
                 SSL_ca => [$caCertHandle]
                 );
}
else
{
     require Net::SSL;
     Net::SSL->import();
}

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

Mac Agent Upgrade

When you're upgrading to 12.0 for the first time, the upgrade-in-place procedure does not apply for Mac agents. For example, when upgrading from 11.4 to 12.0, upgrade-in-place cannot be used.

To complete an initial upgrade to 12.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 12.0 on Mac agents, you can use the upgrade-in-place procedure to upgrade to subsequent 12.x versions.

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

Signiant FIMS Compliant API Updates

To further extend our Signiant FIMS implementation the following improvements have been made:

  • Support for the cleanup command was added to make it easier to clean up or delete a job on the Signiant Manager.
  • To enhance functionality, developers of FIMS REST applications can now generate the FIMS JSON template within the Signiant Manager. This template can be copied or saved for future use.
  • By default FIMS jobs are started immediately, as a result, we've added support for StartJobByTimeType. This functionality allows you to optionally specify when a job is started.
  • To enhance FIMS maintenance, the Signiant Manager and Agents maintenance function has been updated to remove deleted FIMS jobs and the associated job resource IDs.
  • FIMS troubleshooting is now more effective with the FIMS Resource ID column in job views and job details.
  • To make it easier to retrieve a FIMS job failure reason, the FIMS statusDescription has been updated to include the last 10 error and warning messages.

REST API

We have improved our REST API support with the following new functionality:

  • The ability to get users by email address.
  • Listusers provides full user details and includes two optional filters: userType and status.
  • Using deactivateusers and activateusers, administrators can manage the status of users.
  • Listchannels was added to generate a list of channels and channel details.
  • Listusergroups allows administrators to return a list of user groups and user group details.
  • The listusers response has been updated to include user state information. Now using this command, administrators can view state information including the user status, last login attempt, and guest status.

Security

In our 12.0 release, we have made the following security improvements:

  • We have tightened our SQL and JBoss functionality to eliminate any product vulnerabilities.
  • The Core openSSL has been updated to 1.0.2d.

Media Exchange

In response to customer requests and feedback, we've made a range of improvements to Media Exchange in 12.0:

  • The Package Encrypted column has been added to allow reporting on encrypted packages.
  • Media Exchange maintenance has been enhanced to include the agent version and agent build number.
  • To provide improved user reporting, the Package Name column has been added to job reports. This column can be used to understand the number of retries, canceled, and failed transfers users are experiencing.
  • Previously users were automatically locked out of their accounts after one failed login, this required administrator intervention to reactivate the account. Now in 12.0, the Enable User Reactivation option can be used to allow administrators to control failed login behavior.
  • To enhance security and privacy, administrators can choose to hide the email addresses of package recipients from non-administrators.

Reporting and Logging

To further extend our reporting and logging functionality, we've added the following capabilities:

  • In previous releases, scheduled reports for jobs or packages could only be delivered by email. Now in 12.0, these reports can be saved directly to an administrator-designated folder.
  • We have added the Estimated Time To Completion column to the job details and job views pages. This column provides an estimated time to completion for file transfers.
  • The Last Login column has been renamed to Last Login Attempt. This change was made to better indicate that this column includes details on all login attempts, including failed logins.
  • To make it easier to create new job views and reports, administrators can now quickly create a copy of an existing job view or job report.
  • Administrators can now more easily track and manage inactive users with the two new columns have been added to the user view. The Last Successful Login and Last Login Result column data can be used to view user behavior.
  • The job views filters have been updated to include the contains option. Now administrators can choose equals, does not equal or contains.
  • Administrators can use the Queue Time column in the job report to view details on how long a job was queued before it started running.
  • To better enable troubleshooting and to assist customer support, all alarms are now logged in the alarm.log file.
  • To control the behavior of queued jobs, concurrency can be controlled at the Resource Control level. When concurrency is set to 0, no jobs are run.
  • To better troubleshoot maintenance issues, an email is sent to customer support after three consecutive maintenance failures. This email includes the log files for the failures.

User Management

To improve user management, we've made the following updates to 12.0:

  • With a new user setting, administrators can specify the number of hours until user reactivation occurs after a failed account login.
  • Now administrators can view all reports generated by their users. This report data allows administrators to better understand and provide support user problems.

Look-and-Feel

We've made the following enhancements:

  • Context dependent prompts have been added where applicable to streamline the user interface look-and-feel and to simplify administration.
  • To enhance usability, the Transfer Rate graph on the job details screen can be manually scaled.

Browser and Platform Support Changes

Added Manager and Media Exchange GUI browser support for:

  • Mozilla Firefox 38 - 43
  • Apple Safari 9.0.1

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

  • Google Chrome 43 - 47
  • Microsoft Edge 12, 13

We have added Agent support for OS X 10.11.

Manager+Agents 11.4 was the last major product release to include Manager support for Red Hat Enterprise Linux 5.
 
Manager+Agents 12.0 will be the last major release to include Agent support for Mac OS X 10.7 and 10.8. 
 

We have updated our version of supported PostgreSQL to 9.4.1

Limitations

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: http://support.microsoft.com/kb/929851 and http://support.microsoft.com/kb/832017/nl.

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-24200 Only the first 25 User Groups are displayed in the Signiant Manager.
PR-24293 When filtering Packages in Google Chrome 33, the dates are not displayed correctly.
PR-24546 The certificate alarm email doesn't reference the control channel renewal.
PR-24597 Problems with FIMS and job element deserialization.
PR-24608 When changing a password during the Forgot Password process, there is not an indicator that the process is working in the background.
PR-24767 There is a problem related to FIMS and receiving the response object from the Signiant Manager service.
PR-24795 The File List component cannot deal with files larger than 4GB.
PR-24848 Media Exchange downloads display as successfully completed, but the download progress displays as 0 per cent.
PR-24860 Update Job State filtering to use check boxes instead of text fields.
PR-24883 Issues with positioning a Component in a Group on the Workflow Canvas.
PR-24996 The Mac installer should verify hostname resolution before attempting an install.
PR-25078 The Agent installer doesn't correctly configure the Windows firewall.
PR-25129 Media Mover jobs don't delete source files when the source directory name contains more than 248 characters.
PR-25260 Database errors occur when upgrading from 10.6 to a 11.1 or higher version.
PR-25261 Media Gateway DropBox jobs store the Create Jobs as password in plain text in the database.
PR-25296 The Health Check table is not displaying information correctly.
PR-25298 The Web Server allows auto-completion in the Password field.
PR-25310 Published workflows are not importing correctly into version 11.3
PR-25334 SOAP calls are failing or take several minutes to complete.
PR-25342 Media Exchange packages in channels cannot be retrieved.
PR-25357 SOAP call failure occurs during a Media Exchange transfer when all members of the recipient user group are not Media Exchange enabled.
PR-25358 Delivery log entries are not displaying correctly in the Signiant Manager.
PR-25362 The limit path is not enforced in the Prompt Editor.
PR-25382 Legacy workflows that use link trigger commands no longer run.
PR-25385 The authentication web server for agent aliases always defaults to the Manager.
PR-25410 Cannot browse the file system when the Agent field on a template is hidden.
PR-25415 Job reports don't display variable data correctly.
PR-25420 The FIMS Fault Notification does not contain the FaultType object.
PR-25424 Issue with Media Mover and file names that contain spaces being handled properly.
PR-25430 Edited or updated labels in an Workflow are not retained after an import.
PR-25444 Exported templates are becoming corrupted.
PR-25445 Web page error occurs when editing an organization.
PR-25448 Login fails when Active Directory is configured to connect on port 3268.
PR-25453 Dashboard widgets are not displaying the job views that are listed in the Job Views screen.
PR-25468 Legacy templates opened in version 11.1 or newer are displaying incorrectly.
PR-25472 Media Exchange is failing to initialize role collection.
PR-25474 The Maintenance Delete Files process does not run when the host is not resolvable.
PR-25480 The FIMS Rest context type should be application/json not text/json.
PR-25490 The channel expiration period is not honored by Maintenance.
PR-25493 The Transfer API allows the downloading of files outside of the sandbox.
PR-25497 A backup/restore of a template is resulting in a corrupted template.
PR-25501 FIMS callback does not retry when a 502 Bad Gateway message is returned from the load balancer.
PR-25504 FIMS callback is not responding properly when the job priority is changed with the Signiant Manager.
PR-25548 Duplicate consumer_id entries in resource_consumer result in an indefinite queued state.
PR-25550 After editing a default Media Exchange template, it is not possible to exit the screen by clicking OK.
PR-25556 Problem with Media Exchange not correctly displaying the TO and CC email recipients.
PR-25574 Media Exchange transfer is creating a NullPointer in web logs.
PR-25588 Monitoring is turned on an agent when the agent is edited.
PR-25589 The Media Exchange Job Group Resource Control does not work when under load.
PR-25590 Media Exchange Gateway jobs will not upon a retry, use the same delivery folder.
PR-25591 When too many columns are added to a report, only one record is returned in the report.
PR-25594 Downloads don't work correctly when the Media Exchange repository uses lower case characters.
PR-25618 The Health Check workflow fails when the log directory is different from the install directory.
PR-25628 Media Exchange users are logged in with the incorrect profile when the username is entered differently.
PR-25637 Media Exchange package recipients are receiving multiple emails for one package.
PR-25656 After upgrading, Media Exchange links to the repository path have stopped working.
PR-25661 Maintenance does not handle Iteration Group logs properly.
PR-25667 When using the REST API to add group to a channel, the channel property is altered incorrectly.
PR-25686 When creating a job using the REST API, an incorrect BMS.Status message is returned.
PR-25712 The dds_ca check used for running the CA service doesn't handle localhost networking issues.
PR‑25719 When wildcards are used in Agent relays, the entries are duplicated in dds.conf.
 

Known Anomalies

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