Cloud customer?
Start for Free >
Upgrade in MyJFrog >
What's New in Cloud >


Like any software over time, some features and options become obsolete or less useful over time. In some cases, deprecations also occur due to 3rd party end-of-service and end-of-life. In these cases, JFrog makes the decision to deprecate these features and functions, replacing them with a better solution. To make it easier for you see when (in which version) a deprecation occurs, the following document lists the deprecations in the JFrog Platform per version.

We have also linked to this page from the Release Notes of the version in question to make it easier for you to track this information.

Page Contents

Deprecations in Process

The following deprecations are in process. You may want to track them until they go into effect (when they will then move to the relevant product deprecation table).

ProductWhat is being deprecated?TimeframeDeprecation process and next stepsWhat has to be done?
PlatformAuthentication Provider Plugins Deprecated and Replaced With APIs

Deprecated Plugin

Deprecated From


Artifactory release 7.55


Artifactory release 7.57


Artifactory release 7.57

To increase security, JFrog has deprecated a number of authentication provider plugins and replaced them with REST APIs that provide the same functionality.

Additional plugins will also be replaced with APIs in the future.

Deprecated Plugin

Replacement APIs




LDAP Setting


LDAP Group Setting

Use the replacement APIs for these plugins, available from the next Artifactory release.
ArtifactoryAPI Key

API Key deprecation is officially announced from Artifactory 7.47.10 (for Self-hosted customers).

As announced in the Artifactory 7.38.4 release notes, the API Key will be deprecated in the stages for Self-hosted customers (Cloud customers will receive additional instructions). 

The feature will reach end-of-life at the end of Q3, 2023.

The deprecation process of the API Keys will be as follows:

  1. In Artifactory version 7.41.x, administrators were granted the option to block the creation of API Keys to all users using the Artifactory system property.
  2. Artifactory version 7.47.10 includes the option to log users' authentication methods. This will allow administrators to view and warn users using API Keys regarding the upcoming deprecation. 
  3. In a future version (scheduled for end of Q3, 2023), the option to block the usage/creation of API Keys will be enabled by default, with the option for admins to change it back to enable API Keys.
  4. In a later 2023 version, API Keys will be deprecated altogether and the option to use them will no longer be available.
  1. Read this blog post on the API Key deprecation process.
  2. Follow the instructions in the API Key Deprecation Process to learn how to log your users' username and authentication methods.
  3. Begin changing your users' authentication to the 

    new Identity Token format (i.e., a reference token), which can be used to replace the API Keys.

Artifactory SHA-256 checksum support

Artifactory natively supports SHA-256. An artifact's SHA-256 checksum is calculated when it is deployed to Artifactory, and is maintained in persistent storage as part of the database.

The Set Item SHA256 Checksum REST API endpoint (which sets an artifact's SHA-256 checksum as one of its properties) is still supported for backward compatibility, however, this endpoint will eventually be deprecated. 

Artifactory Unexpired password for a single user endpoint
In an upcoming release of Artifactory, JFrog will expire the "Unexpire Password for a Single User" endpoint from RT REST APIs and the UI that goes with it (once API v1 is fully deprecated). This means this API will not available in Artifactory REST API V2.

JFrog Platform Deprecations

The following deprecations have already been implemented in JFrog Platform:

DeprecationVersion/DateDeprecation process and next stepsWhat has to be done?

JetS3t (applies to Self-Hosted environments only)

Artifactory 7.46.3

In continuation to the official email sent on July 22, 2022, we have officially deprecated the JetS3t library that was used in the JFrog Platform to enable an API to AWS S3 and Google Cloud Storage. 

Use the s3-storage-v3 instead, which uses the official, highly-maintained AWS S3 SDK. The transition is seamless between s3 to s3-storage-v3, as most parameters are the same between the two providers. To learn more, see Amazon S3 Official SDK Template.

Docker Build-info 

Artifactory Docker Build-info Plugin 2.14.0

Because version 2.14.0 of the Artifactory Plugin, docker build info creation no longer requires setting up the Build-Info Proxy, the Pipeline API that uses the Build-Info Proxy is now deprecated.

This is the deprecated API:
def rtDocker = Artifactory.docker [credentialsId: 'credentialsId'], [host: 'tcp://daemon IP:daemon port']
You will need to use the new API, which receives an Artifactory server as an argument, instead of credentialsId:
def rtDocker = Artifactory.docker server: server, [host: 'tcp://daemon IP:daemon port']

Ansible Collection installer collectionPlatform Installer July 2021 The Ansible Collection installer, jfrog.installer collection v1.1.2, has been deprecated and replaced. The new installer can be downloaded from
Bamboo Artifactory pluginArtifactory Bamboo Plugin 2.2.0Before version 2.2.0, specifying artifact patterns was possible through Legacy Patterns, which became deprecated in version 2.2.0.No action is required; tasks that were created before version 2.7.0, publish the build-info to Artifactory directly, and not by the Publish Build Info task.
Self-Hosted JFrog Cloud migrator tool 

July 2022

The migrator tool has been deprecated.

Use the new transfer commands available with the JFrog CLI for transferring settings and binaries from a self-hosted JFrog installation to JFrog Cloud. For more information, see Transfer Artifactory Configuration and Files to JFrog Cloud.

TeamCity Artifactory Plugin Legacy Patterns

Artifactory TeamCity Plugin 1.8.0

Legacy patterns have been deprecated since version 1.8.0. These include the custom published artifacts and custom build dependencies.

Artifactory Deprecations

The following deprecations have already been implemented in JFrog Artifactory:

DeprecationVersion/DateDeprecation process and next stepsWhat has to be done?
NuGet V2 APIs Deprecation NoticeArtifactory 7.49.3

With the decision by NuGet for EoL/EoS for Nuget V2 and transition to V3, and JFrog's emphasis on keeping its code up-to-date, the following two NuGet APIs will be deprecated towards the end of Q1, 2023:


If you continue to use NuGet V2, you can use the /search API instead.

CentOS 8.x support

Artifactory 7.43.x

CentOS 8.x reached its end-of-life in December 2021. CentOS 8.x support for JFrog products was deprecated at the end of June 2022. 

Terraform Backend Repository deprecation by HashicorpEnd of Q2 2022

In the first half of 2022, Hashicorp announced the deprecation of a number of legacy providers, including the legacy artifactory provider, which served as a basic backend that only stored States in a generic JFrog repository, created and maintained by Hashicorp.

To avoid confusion, please note that the official JFrog Artifactory Terraform Backend repository, described in this article, is unaffected by the Hashicorp artifactory backend provider deprecation action.

As part of JFrog's alignment with the common Hashicorp main practices, the JFrog Terraform Backend repository supports the official Hashicorp enterprise-grade Terraform backend provider, and supports features such as locking, encoding of the data, smart comparisons, and additional common practices.

KMS encryption client name 

Artifactory 7.31.10

The name, kmsServerSideEncryptionKeyId is deprecated. 

You can continue to use the name without causing any errors.

Use KMS Encryption client with the given KMS encryption key ID or alias. 

Archive search on SaaSDecember, 31, 2021The Archive Search feature in JFrog Artifactory has been deprecated as of December, 31, 2021. The Archive Search feature affects Java workloads by searching through archived JARs and other files. As a result of the deprecation, your Artifactory performance will be improved due to a reduction of upload-related events and a decrease in database-related activities. Browsing JAR archives and associated files will still be available via API or the product UI.

ui/repos/simple/.. path for each repository 

Artifactory 7.17.0

With the release of the new Native browser in Artifactory 7.17, the ui/repos/simple/.. path for each repository has been deprecated and should not be used.


Artifactory 7.9.0The write-locking method and UI session sharing between the JFrog Platform cluster nodes using Hazelcast is no longer supported. For more information, see the Support Blog.

Non-supported Docker strategies for JFrog Cloud users

Artifactory 7.8.1From Artifactory 7.8.1, the subdomain resolution method for resolving Docker repositories will not be supported for new Cloud users. This deprecation does not apply to existing Cloud users.
Breaking deprecation changesArtifactory 7.0
  • All configurations have been moved from the replicator.yaml to the Antifactory system.yaml file.
  • The tx directory, containing temporary data, has been moved to $JFROG_HOME/artifactory/var/bootsrtap/replicator/tx.
  • The proflilingDisabled parameter is deprecated. To enable/disable replicator profiling, use the replicator.profiling.enabled configuration in the system.yaml file.

  • License Control 

  • Stash Search Results .

  • User Plugins: All non-deprecated plugins should now work with Artifactory 7.x. If you wrote a custom user plugin that relies on a non-public API you should test it in Artifactory 7.x before deploying to production.
  • AJP Connector has been removed and will no longer work, HTTP should be used as an alternative.

Xray Deprecations

The following deprecations have already been implemented in JFrog Xray.

DeprecationVersion/DateDeprecation process and next stepsWhat has to be done?
Deprecated integrationsXray 3.0Aqua, WhiteSource, and Black Duck  out-of-the-box integrations have been deprecated in the Xray UI integrations page (Self-hosted)Custom integrations are still available, supporting integrating to any external source of your choice. The VulnDB integration, now transparently integrated into Xray, provides the industry's most comprehensive security vulnerability database. This eliminates the need for these out of the box 3rd party integrations.
Xray homepage in the Platform UI (Self-hosted)Xray 3.0The Xray homepage, as part of the JFrog Platform UI unification, this page has been removed.
Xray 2.0 Reports functionality Xray 3.0
The Xray 3.0 Reports, which are new a functionality, require new permissions
REST API deprecationsXray 3.0

Distribution Deprecations

The following deprecations have already been implemented in JFrog Distribution.

DeprecationVersion/DateDeprecation process and next stepsWhat has to be done?

Target Repository auto-creation checkbox 

Distribution 2.14.1The Target Repository Auto-Creation checkbox has been deprecated.Use the Auto create missing repositories checkbox for the same functionality.

JFrog Peer-to-Peer (P2P) 

Distribution 2.12.3

JFrog Peer-to-Peer (P2P) has been deprecated. 

Use the JFrog Private Distribution Network (PDN), which combines the functionalities of the P2P with JFrog CDN Distribution, giving you the best of both worlds.

Insight Deprecations

The following deprecations have already been implemented in JFrog Insight.

DeprecationVersion/DateDeprecation process and next stepsWhat has to be done?

Elasticsearch Java High Level Rest Client version 7.14.1 

Insight 1.6.0

Elasticsearch Java High Level Rest Client version 7.14.1 used by Insight has been deprecated.The version has been upgraded to Elasticsearch Java API Client version 7.16.2.

Pipelines Deprecations

The following deprecations have already been implemented in JFrog Pipelines.

Deprecation VersionDeprecation process and next stepsWhat has to be done?

Triggering Pipelines from Jenkins jobs

Pipelines 1.6.0

The option to have a pipeline in Pipelines triggered from a Jenkins build job through the build Jenkins publishes to Artifactory has been deprecated from Pipelines release 1.6.0.

It is available only for use with prior releases of Pipelines.

Pipelines 1.6.0

The option to have a pipeline in Pipelines trigger execution of a Jenkins build job through an outgoing webhook has been deprecated from Pipelines release 1.6.0.

It is available only for use with prior releases of Pipelines.

Triggering Jenkins Jobs from Pipelines 

Pipelines 1.26.0

JFrog CLI v1 is deprecated and will be removed. We recommend moving your pipelines to JFrog CLI v2. To make this transition as smooth as possible, all native steps have already been enhanced to support v2.  To update your pipeline to switch to v2, simply add  jfrogCliVersion: 2  to your pipelines.configuration section in your YAML. This will cause the  jfrog  command to point to v2 instead of v1.  

JFrog CLI v1 

1.26.0Helm v2 is deprecated and will be removed. We recommend moving to Helm v3, which is already pre-installed in the default build images. If you are using the HelmDeploy or HelmPublish native steps, you can choose the version in your YAML with the  helmVersion: 3  tag. 
Helm v2

Pipelines 1.23.6

The 1.23.6 release of Pipelines removes support for CentOS 8.x build nodes.

CentOS 8.x build nodes 

Pipelines 1.22.0

The 1.22.0 release of Pipelines removes support for Ubuntu 16 build nodes. 
  • No labels
Copyright © 2023 JFrog Ltd.