Info: Functionality Scheduled for Deprecation

Summary

Occasionally, we remove functionality from Trust Protection Platform to stay current with emerging technologies and to serve the changing needs of our customers. Some of the more common reasons for deprecating features include the following:

• Minimal use of a feature by the majority of our customers
• Technologies that have become obsolete
• Features that have become too expensive to maintain
• Changes in our technology road map 
• Important security enhancements to Trust Protection Platform

See Also:

For a list of features that have been deprecated prior to the current release, visit:

https://support.venafi.com/hc/en-us/articles/115001578651

Scheduled Feature  Deprecations

Although planned feature deprecations are subject to change, the following list indicates which features are planned for removal from upcoming releases of Trust Protection Platform:

Venafi Platform 19.3

POST Credentials/RenameContainer WebSDK Method

This method provides identical functionality to the much more commonly used POST Config/RenameObject method so it will be removed to eliminate customer confusion and simplify support of the API.

Venafi Platform 19.4

Drop Support for SQL 2012 and SQL Server 2014 Support

Beginning in 19.4, Venafi Trust Protection Platform will no longer support SQL Server 2012 and SQL Server 2014. SQL Server 2016 SP1 Standard will be the minimum version that we support.  This is required in order to leverage the Table Partitioning Feature that Microsoft has made available in SQL Server 2016 SP1.

Eliminate Manual Approval option for DigiCert CA

DigiCert has recommended that we update our driver to take advantage of a new "skip_approval" option which streamlines processing on their side for up to a 30% increase in performance.  As a result, Venafi Platform workflow will be the only method for requiring human approval of certificate requests beginning in 19.4.

Xolphin CA driver

The Trust Protection Platform integration with the Xolphin CA will be transitioned from a built-in CA driver to a solution that leverages the Adaptable framework in 19.4.

Venafi Platform 20.1

Remove SSH connection method for the Citrix NetScaler driver

In 17.1, we began the transition from SSH CLI to the NetScaler REST API. When we updated the NetScaler driver and introduced Onboard Discovery. We continued to support the SSH CLI so customers would have time to migrate existing instances over.  After nearly 3 years, the legacy connection method will be removed.

Remove SSH connection method for the IBM DataPower driver

In 17.3, we began the transition from SSH CLI to the DataPower REST API. We updated the DataPower driver and introduced Onboard Discovery. We continued to support the SSH CLI so customers would have time to migrate existing instances over.  After over 2 years, the legacy connection method will be removed.

Splunk driver

In 19.3, we're planning to make significant enhancements to our Syslog driver which we believe, based on feedback from customers and Splunk themselves, will provide an overall better integration path that the Splunk driver which is delivering event data in a manner that is not common for enterprise applications.  Thus the Splunk driver will be removed from the Venafi Platform in 20.1.