Follow

Info: Functionality Scheduled for Deprecation

Summary

Occasionally, we remove functionality from Trust Protection Platform in order 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 18.3

Network Discovery Jobs in Web Admin
Network Discovery job configuration will be removed from the Web Administration console. Beginning in 18.2, you will need to use Aperture for all Network Discovery jobs. Enhanced configuration options for Network Discovery have been available in Aperture since version 14.3.

Network Discovery Placement Preview
The Network Discovery Placement Preview feature will be removed from Aperture. After its removal, Network discovery will work more like agent and TrustNet discovery: items are automatically placed after they are found.

Onboard Discovery will be moved from Web Admin to Aperture
Onboard discovery for F5, NetScaler, and DataPower will only be available in Aperture. These onboard discovery options will no longer be available in the Web Administration Console.

Server Agent Support for SuSE/SLES 10
Long Term Service Pack Support for SuSE/SLES 10 SP4 ended on 31 July 2016.  In 18.1, support for SLES 12 was added so we will be dropping support for SusE/SLES 10 in 18.3

F5 Provisioning/Installation Support for F5 version 10.x
This has been considered a legacy platform for several years and the vendor has ended support in December 2016.  Discontinuing support will allow for removing complexity in coding, usability, testing and support.

GSK Provisioning & Certificate Installation Support for JKS and PKCS#12
IBM Dropped support for the JKS format when they released GSK 8.0 in 2010.  The GSK driver support for JKS and PKC#12 depends upon the software utilities hosted on the remote device which has proven problematic.  Venafi's JKS and PKCS#12 drivers are better suited to handle these use cases because they support central generation of the keystone and now support all of the use cases the GSK driver once uniquely supported.

.NET Framework update
.NET Framework version 4.7 will be required to be installed on Venafi Platform servers.

Tectia 4.x Authorization File Support
SSH discovery and remediation of Tectia 4.x authorization files will be removed. You will still be able to detect and rotate actual key files used in conjunction with authorization files, but not the options.

Certificate Authority Report
The canned Certificate Authority report will be removed. The distribution of certificate authorities by number of issued certificates is available in the Certificate Inventory Report and the Certificate Dashboard in Aperture.

Venafi Platform 18.4

User Portal support for remote installations
Previous to version 18.4, the User Portal (used for requesting user certificates) could be installed on Windows Servers that were not running Trust Protection Platform. Beginning with 18.4, the User Portal will no longer support remote installations and will be part of Trust Protection Platform's standard installation package.

Cisco ACE Certificate Installation Driver
Cisco announced the end-of-life of this product in late 2013. Cisco’s official end-of-support is January 2019.

Layer 7 Certificate Installation Driver
Venafi's technology partnership ended when Computer Associates acquired Layer 7 in 2013.  Venafi has not had the necessary equipment to properly maintain and support this integration. There is also not enough market demand for this integration to justify it to remain a native integration for the platform. Customers using Venafi to integrate with Layer 7 should work with Computer Associates or a third party resource to implement an Adaptable integration with Layer 7.

POST Config/RemoveAttributeValues
The Post Config/RemoveAttributeValues will be removed as a supported method. If misused it can be catastrophically destructive and doesn't offer a valid use that can't be done with other methods.  It was removed from product documentation in 18.2 and will be completely removed in 18.4.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Aaron Hixson

    Article updated on June 19, 2018