Deprecations in Process

JFrog Release Information


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).


What is being deprecated?


Deprecation process and next steps

What has to be done?


Support for Helm client versions under 3.0.0

Verify Connection will be blocked for Cloud users in Artifactory 7.70.x.

This feature will reach end-of-life on February 1st, 2024.

From February 1st, 2024, Artifactory will use Helm client v3 by default, and remove the support for all Helm client versions under 3.0.0.


RubyGems /dependency REST API for local repositories

As announced in the Artifactory 7.58.1 release notes, RubyGems has deprecated their support of the Dependency REST API, and JFrog is removing the support to align with RubyGems. For more information, please read this blog post by RubyGems: Dependency API Deprecation

This feature will reach end-of-life at the end of Q4, 2023.

In December 20th, 2023, Artifactory will remove the support of the Dependencies REST APIs for local repositories.

Use the RubyGems Compact Index REST API instead of the deprecated REST API.

Alternatively, you can configure a reverse proxy workaround and keep using the deprecated Dependencies API.

Find information about both options in this blog post: ARTIFACTORY: Dependency API Deprecation



As notified in Artifactory 7.47.10, support for API Key is slated to be removed in a future release. To ease customer migration to reference tokens, which replaces API key, we are disabling the ability to create new API keys at the end of Q3 2024. The ability to use API keys will be removed at the end of Q4 2024. For more information, see JFrog API Key Deprecation Process.Introduction to the User ProfileJFrog API Key Deprecation Process

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

    • Self-hosted Artifactory version 7.47.10 includes the option to log users' authentication methods. This allows administrators to view and warn users using API Keys regarding the upcoming deprecation. See API Key User Collection for Self-Hosted Customers.API Key User Collection for Self-Hosted Customers

    • Cloud Artifactory version 7.63.5 includes the option to view and download the list of users using API Keys regarding the upcoming deprecation. See API Key User Collection for Cloud Customers.API Key User Collection for Cloud Customers

  1. By the end of Q3, 2024, you will not be able to create new API keys through UI or API.

  2. By the end of Q4 2024, we will no longer support API keys.

  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.API Key

  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.Introduction to the User Profile


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.


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.