Deprecations

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.

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.security.apiKey.blockCreate 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 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. 

JetS3t (applies to Self-Hosted environments only)

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. 

Docker Build-info 

Artifactory Docker Build-info Plugin 2.14.0

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']

July 2022

The migrator tool has been deprecated.

TeamCity Artifactory Plugin Legacy Patterns

Artifactory TeamCity Plugin 1.8.0

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:

        /GetUpdates()
        /GetUpdates()/$count

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

CentOS 8.x support

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. 

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 

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. 

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

Artifactory 7.17.0

Hazelcast 

Non-supported Docker strategies for JFrog Cloud users

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

• AUTHENTICATION
  • Get Token
• USER MANAGEMENT
  • Create User
  • Update User
  • Delete User
• BINARY MANAGERS
  • Add Binary Manager 
  • Update Binary Manager 
  • Delete Binary Manager
• LICENSE REPORTS
  • Generate License Report
  • Get License Report
  • Get License Report Components
• SECURITY REPORTS
  • Generate Security Report
  • Get Security Report
  • Get Top Vulnerabilities Security Report
• GRAFEAS
  • Get Note
  • Update Note
  • Create Note
  • Delete Note
  • Get Occurrences by Note ID
  • Get Occurrences by Component ID
• SYSTEM
  • External Ping Request
• PERMISSIONS
  • Get Permissions
  • Get Permission Details
  • Create Permission
  • Delete Permission

Target Repository auto-creation checkbox 

JFrog Peer-to-Peer (P2P) 

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

Elasticsearch Java High Level Rest Client version 7.14.1 

Insight 1.6.0

Triggering Pipelines from Jenkins jobs

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.

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 

Pipelines 1.23.6

CentOS 8.x build nodes 

Pipelines 1.22.0