Artifactory 7.63

JFrog Release Information


Issue ID


Fix Version

Additional Information


When publishing an npm package with a size exceeding 5 MB, Artifactory returned an error.



When assigning a virtual repository to a project, no validation is performed. Validation is performed only when the assigned virtual repository is changed. This means that an invalid repository can be assigned to a project, and no configuration changes can be made to the virtual repository.


Two possible workarounds:

  1. If you want to make configuration changes to the virtual repository, you should unassign the virtual repository from the project, remove all repositories underneath the virtual repository, and then reassign the virtual repository back to the project. You can then add back any valid repositories to the virtual repository.

  2. You can share the virtual repository instead of assigning it to a project.


When updating Artifactory to version 7.63, under some circumstances, users who attempt to modify their binarystore.xml configuration file might experience files being deleted.


Users with Sharding Cluster configured with Eventual Cluster are at risk of experiencing this issue.


When restoring an archived package, the summary displays invalid data about the number of items restored (referring to artifacts) and the success percentage.


The total displayed is correct with respect to packages, but it does not correspond with the number of artifacts restored.

The success percentage is meant to be calculated based on:

[total number of packages]/[completed number of packages]

RTDEV- 34236

When using Artifactory versions newer than 7.56, under certain circumstances some large accounts might experience a high query load to the PostGreSQL database, causing it to crash.

Customers with the one of following account specifications should use the workaround specified:

  • A database Nodes table containing over 200 million rows

  • Over 5% of the database Nodes table contents refer to Docker images or Maven packages


Workaround: To avoid this issue, set the following system property: artifactory.file.service.cache.enabled=false


If your virtual repositories point to less than 10 local repositories each, it is recommended to disable this feature using the system property above.


When creating a retention policy for archiving packages and the number of packages is more than 10,000, if you preview the policy status the number of artifacts shown in the preview corresponds to the first 10,000 packages only.


All artifacts for all packages are actually archived, however, the preview can only display the number of artifacts for the first 10,000 packages.


Customers in versions 7.59.x-7.63.5 who created authentication SSH keys under User Profile and then upgraded to a newer version will lose the saved authentication SSH keys.


Check if your SSH keys have been lost, and if so, upgrade Artifactory to version 7.71.16 and recreate the SSH keys.


When using Artifactory version 7.55 and above, under certain circumstances, when performing a Crowd group search, accounts with a large number of Crowd groups (above 10,000) might experience slower performance on the Crowd/JIRA page in the JFrog Platform WebUI.




When selecting to Manage Resources as part of Project settings, because Projects are not federated resource management is not federated to other JPDs.