R18-3 HF3.2 Release Notes

Resolved Issues from Previous Releases

Tufin Orchestration Suite (TOS) R18-3 HF3.2 includes all resolved issues listed for this release, as well as all resolved issues from the previous releases listed below.

All Resolved Issues

 

 
This release
R18-2 HF3 and below
R18-1 HF3.2 and below
R17-3 HF4.1 and below ST SC SA

Upgrading Tufin Orchestration Suite

You can upgrade to Tufin Orchestration Suite (TOS) R18-3 from R17-3, R18-1, or R18-2. To upgrade from earlier versions than shown above, first upgrade to TOS R17-3, R18-1, or R18-2 and then upgrade to TOS R18-3. Make sure to read the additional notes in the Release Notes for each version upgrade.

Upgrading to Tufin Orchestration Suite R18-1 and above requires TufinOS 2.14 or above, RHEL 6, or CentOS 6.

Click here to view the Tufin Orchestration Suite build number history.

The complete Tufin Orchestration Suite documentation can be found in the Tufin Knowledge Center.

Upgrading TufinOS

  • Installing TOS for the first time on a server running a clean install of TufinOS 2.15 or above, requires TOS R18-1 or above.
  • Upgrading or installing on a server after you have upgraded the server to TufinOS 2.15 or above, requires one of the following TOS versions:
    • TOS R17-3 GA or above
    • TOS R17-2 HF2.2 or above
    • TOS R17-1 HF4.1 or above
    • TOS R16-4 HF5.1 or above
  • If you are running TOS R16-3 or below you must first upgrade TOS to the desired version using the latest hotfix available, and then upgrade TufinOS.

Additional Information

  • If you are running a Distributed Deployment architecture, the upgrade will transfer the SSL certificate from the Distribution Server to the Central Server. The installation script will prompt for the SecureTrack administrator account credentials, so have the credential information available prior to beginning the upgrade.

  • If you use CA-signed SSL certificates, you must use the SSLCertificateChainFile directive rather than the SSLCACertificateFile directive. See TufinOS Prerequisites or Non-TufinOS Prerequisites in the Security Essentials section of the Knowledge Center.

  • Preserve your SSL certificate and configuration customizations during an upgrade to Tufin Orchestration Suite. See Customizing SSL or Virtual Host Configuration for details. (for R17-3 HF3 and above)

  • Prior to upgrading to R17-3 or above you must fill in the "Administrator DN" field (SecureTrack > Settings > Configuration > External Authentication). After the upgrade has completed, the title of the field will be renamed to "LDAP Bind DN".

  • If your TOS deployment uses a Distributed Architecture configuration, you may need to upgrade sTunnel. See sTunnel Patch Installation Instructions in the Customer Portal for details.

  • Policy Advisor reached its “end of life” (EOL). Use the expanded and enhanced capabilities provided by SecureChange Designer to plan and provision changes to device policies.

  • Creating and updating a SecureChange ticket via SOAP protocol will reach it's “end of life” (EOL) support effective TOS R18-1. Use the expanded and enhanced functionality provided by the SecureChange REST APIs to create and manage change requests.

  • Support for Microsoft Azure Classic devices has reached it's “end of life” (EOL) support in TOS R17-2. Tufin now supports Azure Resource Manager. All Azure Classic devices that are being monitored by SecureTrack will be removed during the upgrade process. We recommend that you backup TOS and archive the backup file, to retain policy change history and other relevant information for future reference.

  • TufinOS 1.x reached its “end of life” (EOL) support on March 31, 2017, at the same time as Centos 5. No updates or security patches will be created for TufinOS 1.x. Tufin Orchestration Suite R16-3 and R16-4 are the last two versions of TOS that are supported for TufinOS 1.x. We strongly recommend that you migrate to TufinOS 2.x. See Migrating to TufinOS 2.x for migration details.