Artifactory 7.77.6 Self-Hosted

JFrog Release Information


Released: 29 February, 2024

Operating Systems - End of Support

As part of JFrog commitment to maintain the security and reliability of the JFrog Platform, Artifactory will officially run with Node.js 20.x on all installation types from Artifactory 7.77.3.

Node.js 20.x provided with Linux Archive/Debian/RPM installations (non-containerized distributions) is not supported on the following operating systems.

Hence, these operating systems will no longer supported from Artifactory version 7.77.3.

Feature Enhancements

  • npm Package Type added for Cold Storage Archiving

    It is now possible to archive npm packages in Cold Storage. For more information on archiving in Cold Storage, see Working with Cold Storage.Working with Cold Storage

  • Advisory locks for PostgreSQL

    Self-hosted Artifactory users with PostgreSQL now have the option of using a database locking mechanism based on advisory locks instead of the previous mechanism, which is based on distributed table locks. Advisory locks help reduce the problem of database table bloating, which increases database storage consumption and has been known, in some cases, to overload the database server CPU and increase the duration of lock/unlock operations. For more information, see Configure Artifactory to Use Advisory Locks in PostgreSQL.Configure Artifactory to Use Advisory Locks in PostgreSQL

  • Automatic Association of Groups for SAML Users in Identity Tokens

    When you create an identity token for a SAML user, all the groups associated with the user in the SAML configuration are included in the token scope.

Resolved Issues

JIRA Issue





Fixed an issue whereby, when trying to remove an SSH key from Artifactory, the key was not completely removed.



Fixed an issue related to RPM whereby, when trying to resolve artifacts from an upstream repository through a virtual repository, Artifactory did not work as expected at first attempt.



Fixed an issue related to Conda whereby, when trying to deploy an artifact with an empty noarch metadata value, Artifactory did not calculate the package metadata as expected.



Fixed an issue whereby, 'unexpected parameters count' warning messages appeared in the Artifactory logs unnecessarily.



Fixed an issue whereby the Small Garbage Collection pruning query took a long time due to redundant trash.time node properties that were created on directories. Artifactory now stops creating new trash.time properties for directories and a new API is available (Delete Redundant Records to Trash Can Directories) to delete all redundant trash.time properties in Trash Can directories.Delete Redundant Records to Trash Can Directories



Fixed an issue related to Maven whereby, Artifactory did not force authentication for unavailable artifacts in virtual repositories in the native JFrog Platform WebUI even when the Force Authentication checkbox was selected.



Fixed an issue related to Go and PyPI whereby, when resolving artifacts from remote repository using a plugin that uses the org.artifactory.exception.CancelException class, Artifactory returns an incorrect error.



Fixed a permissions issue that prevented users with a license other than Enterprise+ from creating Release Bundles v2 from the Release Lifecycle Management dashboard.Manage the Release Lifecycle Using the Dashboard



Fixed an issue whereby, when updating to Artifactory version 7.77.3 and trying to set up a Maven client, Artifactory returned an error.



Fixed an issue whereby, when changing Nginx internal ports to 8080/8443 and nginx.service.ssloffload was set to false, the Artifactory Helm Charts encountered redirection