Artifactory 7.41.4 Cloud | Self-Hosted

JFrog Release Information


Released: July 11, 2022


ARM64 Support

From version 7.41.4, Artifactory supports installation on ARM64 architecture through Helm and Docker installations. You must set up an external database as the Artifactory database since Artifactory does not support the bundled database with the ARM64 installation. Artifactory installation pulls the ARM64 image automatically when you run the Helm or Docker installation on the ARM64 platform.

Swift Registry Supported on Self-Hosted deployment

Swift Registry support has been expanded to support both cloud and self-hosted deployments. For more information, see Swift Registry.Swift Registry

Feature Enhancements

Debian Repository includes Support for Debian Snapshots

From Artifactory 7.41.4, Debian repositories include support for Debian Snapshots and can be used in the following scenarios:

  • As backups, allowing you to easily fall back to previous versions in case of package corruption due to dependency changes.

  • For release purposes, whereby the tested Packages file can be immutably saved and served.

For more information, see Working with Debian Snapshots.Debian Repositories

Conan Search Optimization

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

Updated the Refresh Token Mechanism

To enable refreshing a token without having to provide the old token, a new column has been added to the database that contains the token payload, the token version, and `kid` as a JSON (this is application for refreshable tokens only!). Upon receiving a token request to refresh, the original data is then taken from the new column in the database. For more information, see Refresh Token.Refresh Token (Deprecated)

Maven Snapshot Version Default Behavior Change

Breaking Change

The Maven snapshotVersionBehavior parameter that was set as 'non-unique' as the default in earlier Artifactory versions, is now set as 'unique'. This change affects both local and federated repositories.

Users with Repository Management/Deploy Permission can View/Use the Trash Can Repository

Until the current release, users who did not have Admin permission were unable to view or to use the Trash Can repository, so that only administrators were able to see and interact with the Trash Can. With this release, two changes have been implemented:

  • Users who have deploy or manage permissions to any repository will be able to view the Trash Can and view files in that repository of origin.

  • Users who also have delete permissions to their repository will now also be able to restore them without requiring admin assistance (they will not be able to view or restore any other repositories).


The contents of the Trash Can are filtered based on the repositories to which the user has permissions. This means that the user will not see or restore files from any other repository unless they have permissions to that repository. For more information, see Trash Can Settings.PermissionsTrash Can Settings

Resolved Issues

JIRA Issue



Fixed the issue, whereby running the Create Virtual repository REST API allowed duplicating the same local repository in the Virtual repository.


Fixed an issue whereby, attempting to move files to a virtual repository caused files to disappear.


Fixed an issue whereby, creating permission targets using the REST API was faulty.


Fixed an issue whereby, NPM Info did not include all the artifact data collected from the package.json file.


Fixed an issue whereby, under certain circumstances, NuGet v3 packages containing a version with upper case characters in the 'Prerelease' parameter were omitted from the registration item results if they were in the lower or upper entry of the list.


Fixed an issue whereby, converting a local repository to a federated repository removed the repository from the Project.


Fixed an issue whereby, Helm charts containing annotations with a regex of '[0-9] +e [0-9]' broke the index.yaml.


Fixed an issue whereby, the Npm Info did not include all the artifact metadata that should have been collected from the package.json file.


Fixed an issue where beforeDownloadRequest callback is not working with the NPM Virtual repository.


Fixed an issue whereby, Debian Source packages could not be downloaded if the 'Store Artifacts Locally' option was disabled.


Fixed an issue whereby, uploading Docker images to Federated repositories did not sync to other federated members if the repository name contained more than 34 characters.


Fixed an issue whereby, users with the Manage Resources role could not create the permission targets through REST API.


Fixing an issue whereby, converting local repositories to federated repositories removed the repository from the Project.


Fixed an issue whereby, the GAVC Search returned artifact versions without the SNAPSHOT.


Fixed an issue relating to npm packages, whereby the npm client configured opposite a virtual repository and the remote repository within this repository is offline, the npm audit command fails. This audit command should return results as Artifactory is connected to Xray and therefore should return the results from Xray.


Fixed an issue whereby, under certain circumstances, Go Virtual repositories may have returned a 404 response when the remote repository response was 200.


Fixed an issue whereby, reference tokens expired earlier than expected.

Known Issue in this Version

Affected Audience: Users who have run their remote or federated repositories without a proxy and have manually removed the proxy.

Upgrading to the 7.41.4 version automatically populates the default proxy on all repositories that have manually set the proxy field as empty. To learn more, click here.