Artifactory 7.3.0 Cloud

JFrog Release Information


Released: 23 March, 2020

Artifactory 7.3 is Available as a Cloud Version

The Artifactory 7.3 release is available only as a Cloud version. Artifactory 7.3.2 applies to on-prem and contains all the resolved issues in Artifactory 7.3.0 and 7.3.1.


PAT (Personal Access Token) Support for Remote Repository Authentication

In addition to the basic authentication, with username and password, Artifactory now supports remote repository authentication using Personal Access Tokens (PAT). The big advantage of using PATs is that you can strengthen your Artifactory security practices by using Access Tokens for authentication instead of using your primary credentials. For example, you can configure your remote Docker repository to point to GitHub and authenticate it by using a PAT. You can use PATs for any package type. For more information, see Remote Credentials.Advanced Settings

LDAP Improvements

Artifactory now supports a new type of Active Directory "Nested Groups" search, enabling performance improvements when working with LDAP. This feature requires that Active Directory runs on Windows Server 2012 R2 version or later. There are no additional requirements for the Active Directory Windows Server side. For more information, see Support for Nested Groups.Entra ID

Write-disabled Mode Supported for Shard Storage Requests

To enhance storage sharding, Artifactory now supports disabling write-requests to shards.

This is useful, for example, when migrating data from a shard that must be replaced. First, the feature is used to write-disable the shard and then the data is migrated to a new shard.

In addition, the feature still allows garbage collection to continue to clean the deleted binaries from the write-disabled shard.

To set the write-disable mode on a shard in Artifactory, see the Configuring State-AwareBinary Provider section.Filestore Configuration

Support for Matrix-params with Conan Repositories

Artifactory now supports matrix parameters for Conan repositories. As a result, the Build Info for Conan packages uploaded to Artifactory SaaS is now available.

Feature Enhancements

Restricting System and Repository Imports

Artifactory allows admin users to import and export data at both the system level and the repository level. For more information, see Import and Export.Import and Export

Sometimes, however, it is advantageous to restrict imports to avoid causing undesirable results. With this new feature, the system and repository import options can be disabled, thereby preventing specific admin users in the enterprise from performing imports. For example, you can stop an admin from overriding the Release Bundles distributed to an Artifactory Edge, by preventing them from importing the initial Artifactory state.

Resolved Issues

JIRA Issue



Fixed an issue where Artifactory did not start as a service on RedHat 7.7 and Centos 7.7 when upgrading Artifactory from versions earlier than 6.14.0.


Fixed an issue where Docker Image failed to start with Oracle DB because Artifactory's Docker entry point could not get the endpoint of the external Oracle DB.


Fixed an issue where, even if the user had Deploy Permissions for the default deployment repository in the virtual repository, Set Me Up would incorrectly issue the following warning message:

You do not have deploy permissions to this repository.


Fixed an issue whereby in some cases of a load-balanced remote repository, where two nodes are out-of-sync, a conflict between the metadata of a file and the contents of the file might result.


Fixed an issue where pulling an image from a smart remote Docker repository always causes it to pull the manifest.json file from the source Artifactory. This behavior would cause a failure if the Artifactory source instance was not reachable.


Fixed an issue where, after a pull replication was executed from a Docker smart remote repository, which was pointing to a Docker remote repository that in turn was pointing to a Docker Hub, Artifactory was not able to serve the artifacts from the local cache when the Docker smart remote repository was set to offline mode.


Fixed an issue where the latest npm package was always being determined by the publish date, regardless of the artifactory.npm.tag.tagLatestByPublish system property value.


Artifactory now supports the new Maven XML tag attributes that were introduced with Maven 3.6.x.


The Go remote GitHub repository can now resolve both incompatible and compatible Go Module v2+ project version formats.


Fixed an issue where the checksum for a Go module that was directly resolved from GitHub differed from the checksum when the module was resolved from or


Fixed an issue where Debian packages that did not contain control files would cause metadata resolution to fail when the $ apt update command was invoked.


Fixed an issue that resulted in Artifactory generating incorrect metadata for some CRAN package types.


Fixed an issue whereby viewing Docker images stored in a remote-cache displayed a hash symbol instead of a tag.


Fixed an issue whereby the port used for Artifactory authentication in Artifactory 7 (8082) differed to Artifactory 6.0 (8081) causing backward compatibility to fail.


Fixed an issue whereby upgrading to Artifactory 7.x caused the internal Hostname to be set to Artifactory instead of being configured as the IP address of the Artifactory server.


Fixed an issue whereby the SHA256SUMS file was not tracked as an IDK in Debian Remote repositories.


Fixed an issue whereby PyPI redirections did not recognize the value of the X-JFrog-Override-Base-Url header.


Fixed an issue whereby users (that are not defined as admins) in any group defined as an Admin group could not generate Join Keys.


Fixed an issue whereby indexing Helm Charts failed during high concurrent indexing.


Fixed an issue whereby, hijacked sessions caused a memory leak in the JFrog Router service.

For a complete list of changes, please refer to our JIRA Release Notes.