Artifactory 7.29.7 Cloud | Self-Hosted

JFrog Release Information


Released: 5 December, 2021


New Hybrid Solution Provided through the Distribution Edges

Self-hosted customers who have an existing JFrog Distribution in place may sometimes require the option of adding additional JFrog Artifactory instances in the cloud. This hybrid setup is now supported through the JFrog Distribution Edges Add-on, a commercial offering for On-Prem customers to leverage JFrog SaaS for software distribution. This add-on enables On-Prem customers toadd cloud-based Edge nodes managed by JFrog (software-as-a-service) and fully utilize them for content distribution. See Configuring Distribution Edges Using the Distribution Edges Add-on.Hybrid Distribution from JFrog Platform Self-Hosted

New Integration for JFrog Artifactory with Amazon's Elastic Cloud Kubernetes (EKS) Anywhere

Amazon's Elastic Cloud Kubernetes (EKS) Anywhere is a new deployment option for Amazon EKS, which allows customers to create and operate Kubernetes clusters on customer-managed infrastructure, supported by AWS. Unlike the Bring Your Own License (BYOL) model, which uses a Docker image, the deployment of JFrog Artifactory on Elastic Cloud Kubernetes (EKS), EKS Anywhere uses Helm Charts to leverage the AWS License Manager. See Artifactory Integration with Amazon AWS Container Marketplace.Artifactory Integration with Amazon AWS Container Marketplace

Support for Personal OAuth SSO

JFrog Cloud users (only) can now also join through an invite, and to then log in using Personal OAuth such as Google or GitHub. For more information, see Adding New Users via Invite.Introduction to Users and Groups

Master.key Load and Retention in Memory

To improve security around the storage of the master.key, from Artifactory version 7.29.7 JFrog supports loading the master.key at startup and keeping it in memory. This is achieved by removing the master key from the file system by each application, after it was read by the application node during bootstrapping. Customers who wishing to utilize this capability will need to "opt-in" to the master key removal, to fetch the master key and to place it in the correct path on the application's file system whenever a new node is bootstrapped. See Master.key Load and Retention in Memory.Access YAML Configuration

Feature Enhancements

Garbage Collection Performance Improvements

Improved Garbage collection performance by implementing changes to the internal garbage collection batch mechanism.

New Pairing Token UI and API

Added new UI in the JFrog Platform for a pairing token, which establishes trust between different JFrog micro services. The pairing token is an access token that is used for the initial pairing flow. Because the token is a limited access token, it is dedicated to a specific task and short-lived. Once trust is established, the services can continue using the standard token-based authentication for communication. Pairing tokens replace the join.key that was used in the past in the JFrog Platform to link between services. This type of token is only designed to link cross-topologies (i.e., locally, and not with in a JPD). See Generating Scoped and Pairing Tokens.Generate Scoped Tokens

NuGet Repository Improvements

As part of the NuGet package improvement initiative, we have added the ability to resolve cached artifacts from remote NuGet repositories in case the remote repository is down.

Hiding Artifactory Version in the UI is Supported

The Artifactory version in the UI can be hidden by setting the to the var/etc/artifactory/ file.

This feature is applicable only to Artifactory Self-hosted instances.

Conan Search Optimization

Performed internal changes to the Conan search resulting in Conan search optimization.

Resolved Issues

JIRA Issue



Fix an issue whereby, PowerShell Invoke-WebRequest requests would redirect to the UI.


Fixed an issue whereby, Docker remote and virtual repositories did not display the correct Xray Blocked message.


Fixed the issue whereby, a new repository could not be created by the project admin when the Exclude New Repo option was enabled in the backup configuration.


Fixed an issue whereby, the Native UI browser did not list any files under a repository and its subfolders when an "Include Patterns" was configured.


Added the ability to resolve cached artifacts from remote NuGet repositories in case the remote repository is down.

Fixed an issue whereby, offline Artifactory nodes could not be deleted from the Service Status page in the UI.

Fixed an issue whereby, Artifactory pointed to the incorrect remote Conan repository. The Default URL for the remote Conan repository was changed to

Fixed an issue whereby, the Topology page in the UI was not loading.

Fixed an issue whereby, the Graph view located under the Packages page did not load.

Fixed an issue relating to Federated repositories whereby, remote Federated repositories were not visible in the available Remote Platform deployments.

Fixed an issue whereby, the service version was not displayed in the Service Status page in the UI.

Fixed an issue whereby, setting up a star topology between Artifactory Edge nodes did not propagate the permissions from one Edge to another.

Fixed an issue whereby, an Access Config Backup file was generated even if no changes were made to the configuration.

Fixed an issue whereby, performing DB migration from 7.17.x to 7.27.6 failed, if the sql_require_primary_key was enabled.

Fixed an issue whereby, two Mission Control services became available after upgrading from an Artifactory version with Mission Control to an Artifactory with Mission Control set as an internal Artifactory service.

Fixed an issue whereby, setting up Federated repositories required setting up a proxy.