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://docs.venafi.com/Docs/current/TopNav/Content/Release-Documents/Deprecated_Functionality_From_Venafi_Platform.php

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 21.4

User Agent (AJ) and User Portal no longer available in 21.4

As part of our rebranding of the Endpoint Protect product being updated to Client Protect, we are removing features such as the User Agent (sometimes referred to as AJ) and the User Portal.  These are no longer available in the Client Protect product in 21.4 and going forward.

19.4 Code Signing Client must be Upgraded
In 21.4 of CodeSign Protect will no longer support the code signing clients from 19.2-19.4. The undocumented REST APIs that supported these older client versions are being removed.  Prior to upgrading to 21.4 or higher, please upgrade your code signing clients to more recent versions.

Venafi Server Agent on HP-UX 

We intend to stop producing new releases of Venafi Server Agent on HP-UX (Itanium) with the 21.4 release, making the 21.3 release the the last to include support for the platform. 

VAM nShield Certificate Installation Driver Deprecation
Starting in 21.4, application objects for VAM nShield Certificate Installation instances will be converted to basic application objects.

Venafi Platform 22.1

Pass-through Authentication
With the release of SAML support, we plan on deprecating the support for pass-through authentication. Before SAML was introduced, Pass-through authentication is the mechanism that was used to integrate with Oracle Identity and Access Manager (IAM).  If you are using IAM with the Venafi Trust Protection Platform, please update your configuration to leverage SAML prior to upgrading to 22.1 or higher. 

WebSDK Authorization Method involving API keys is only available with a License Key
Starting in 22.1, only customers with a special, temporary license key from Venafi will be able to leverage WebSDK API Keys to authenticate to the WebSDK.  Without the license key, both POST Authorize and the WebSDK Permission will not be available.

Imperva MX will support provisioning of device certificates only
Starting in 22.1 Imperva MX driver will be able to provision device certificates only. After upgrading to 22.1 existing Imperva MX applications will be converted to Basic applications and retain certificate association. Provisioning certificates in bulk to Imperva MX can be accomplished using the Adaptable Bulk Provisioning job.

Removal of three detail screens from the About section of the Web Console

Starting in 22.1, the following three screens will be removed from the Web Console About section:

• Loaded API Assemblies
• Loaded UI Plugins
• Third Party UI Libraries
  

These screens were originally included to aid in troubleshooting of problems related to the Web Console, but instead were rarely, if ever used.

Venafi Platform 22.2

WebSDK Authorization Method involving API Keys (End-of-Support)
The WebSDK authorization method that involves API keys was formally deprecated in Trust Protection Platform 20.2 and will no longer be available in code beginning in 22.2.  The "WebSDk" permission that is available on users and groups will no longer be available.  The temporary license key introduced in 22.1 will no longer be available.