Artifactory 7.77.3 Self-Hosted

JFrog Release Information


Released: 24 January, 2024

Artifactory 7.77.3 is Available as a Cloud and Self-Hosted Version

Artifactory 7.77.3 is the Self-Hosted version and contains all the highlights, feature enhancements, and bug fixes stated in Artifactory 7.77.1 as part of our Cloud-first initiative.


A new database locking mechanism for self-hosted users with PostgreSQL was announced in 7.77.6, but is available starting from 7.77.3. For more information, see the 7.77.6 Release Notes and Configure Artifactory to Use Advisory Locks in PostgreSQL.Configure Artifactory to Use Advisory Locks in PostgreSQL

Integration Service Sunset

The Integration service has been deprecated. For more information, see Artifactory Deprecations.

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.

Update in the NGINX Image

The Nginx image used in Artifactory installation (for Helm, Docker Compose, and Docker installations) has been modified so that all processes inside the container can now bind to any port (of the container) including ports lower than 1024. The external ports are still 80 and 443 for HTTP and HTTPS respectively.

If you run the Nginx container with a container engine that have restriction regarding binding of lower ports or use custom values for ports in the values.yaml, and face issues, you must adjust accordingly or remove port restriction from your setup.

Highlight: Hugging Face GA

Breaking Change for Hugging Face

Using Hugging Face GA may break your local repositories and make your stored Hugging Face models inaccessible by Hugging Face REST API due to layout changes. Please re-deploy all of your Hugging Face models in local repositories to ensure consistent performance. For more information, see Hugging Face GA Repository Structure Migration.

  • Support for New Hugging Face Repository Structure

    Artifactory now uses a new repository layout for Hugging Face, allowing you to store several revisions under one integration version. For more information, see Hugging Face Repository Structure.Hugging Face Repository Structure

  • Federation support for Hugging Face

    It is now possible to create Federated repositories based on the Hugging Face package type.Federated RepositoriesHugging Face Repositories

  • Support for Private Hugging Face Repositories

    Artifactory now supports resolving private Hugging Face models from Hugging Face Hub using authenticated access. For more information, see Resolve Hugging face Models from Private Repositories.Resolve Hugging Face Models From Private Repositories

New Features

  • Self-Hosted Support for OCI Registry

    You can now use OCI registry version 1.0.2 natively in Artifactory as its own package type, so you can manage and save your OCI containers in Artifactory while providing full flexibility and usability.

    For more information, see OCI Registry.OCI Registry

  • Self-Hosted Support for Helm OCI Repositories

    You can now use OCI to package Helm charts, making it easier to scale, distribute, and leverage the power of OCI to deliver charts.

    For more information, see Helm OCI Repositories.Helm OCI Repositories

  • Support for Nginx in OpenShift Installation

    Artifactory now supports Nginx in OpenShift installation.

  • Automatic Recovery in Access Federation

    Access Federation now supports automatic recovery for stale services. For more information, see Revive a Stale Service.Revive a Stale Service

  • Conflict Resolution in Access Federation

    Access Federation now has advanced conflict resolution to resolve conflicts in the updates between JPDs. For more information, see Conflict Resolution in Access Federation.Conflict Resolution in Access Federation

  • OpenID Connect Integration

    OIDC integration in the JFrog Platform allows you to use services such as GitHub Actions with OpenID Connect to work on the JFrog Platform. With OIDC integration, you can allow the GitHub Actions CI pipelines to download and publish artifacts without storing JFrog passwords, tokens, or API keys in GitHub.

    OpenID Connect Integration is now available for the self-hosted JFrog Platform and has been available for JFrog Cloud since Artifactory version 7.73.1.OpenID Connect Integration

    OpenID Connect integration provides the following benefits:

    • Passwordless experience The integration eliminates the storage of Secrets in GitHub Secrets.

    • Enhanced security Fine grained Token upon Identity

    • Seamless token management  The integration eliminates the need to manually handle and manage tokens.

  • Custom Global Roles

    You can now create, define, edit, and delete custom global roles in the JFrog Platform. Custom global roles are high-level roles that can be created at the global level and can be applied to all projects. A global role allows project Members assigned with the role from any project to perform a defined set of actions.Create Custom Global Roles

  • Next Generation Permissions

    The next generation of permission model (Permissions V2) is now available in the self-hosted JFrog Platform. The new model is fully backward compatible with the legacy permissions (Permissions V1) model. The new model simplifies the UI user flows to configure all resource types. The popups to add resource type (like builds and repositories) have a new look and feel.

    For more information, see Permissions.Permissions

  • Webhooks Troubleshooting

    You can now view webhooks troubleshooting data in the JFrog Platform UI. You can configure whether to display only the failed events or all events of a webhook. For more information, see View Webhooks Troubleshooting Data in the UI.View Webhooks Troubleshooting Data in the UI

  • Passwordless Access for Amazon EKS

    JFrog Platform can leverage AWS AssumeRole to provide passwordless access experience in Amazon EKS. AssumeRole authentication method allows AWS users to use roles assigned to them to create temporary authentication tokens that can be used in the JFrog Platform.

    You can leverage this feature when you use a JFrog Platform Installation on an Amazon EKS cluster. For more information, see Passwordless Access for Amazon EKS.Passwordless Access for Amazon EKS

Feature Enhancements

  • Improved Balancing in the Sharding Binary Provider

    The process of balancing in the Sharding Binary Provider was improved such that the retrieval of binaries from the active providers skips the cache.

  • Performing a system import with active repository Federations

    It is now possible to perform a system import on an Artifactory instance that has active repository Federations. For more information, see System Import and Active Repository Federations.System Import and Active Repository Federations

  • Additional Full Sync event properties for Federated repositories

    Two new event properties are available when performing Full Sync operations on Federated repositories. These new properties retry the attempt to create event bulks (or batches) if the initial attempt fails. For more information, see Configure Federated Repositories for Bulk Event Mirroring and Parallel Processing.Perform Full Sync on Federated RepositoriesFederated RepositoriesConfigure Federated Repositories for Bulk Event Mirroring and Parallel Processing

Resolved Issues

JIRA Issue





Fixed an issue related to CocoaPods whereby, when configuring a remote repository using CocoaPods CDN, Artifactory did not support the 'pod repo update' command.



Fixed an issue related to npm whereby, when copying a package to a different repository, after removing the package with the disttag=latest, the package.json metadata file was copied as empty.



Fixed an issue related to Terraform whereby, when using a statefile weighing more than 20MB, the backend repository returned a 400 error.



Fixed an issue related to Terraform whereby, under certain circumstances, modules from remote repositories could not be resolved due to a Terraform update.



Fixed an issue whereby, when promoting a build with more than 1,000 modules using the Oracle database, the promotion failed.



Fixed an issue related to Docker whereby, when using HTTP single sign-on authentication and performing certain REST API requests, Artifactory might return an error.



Fixed an issue whereby, when using a curl command with a ‘range’ HTTP header to fetch bytes from the end of a text file, Artifactory fetched bytes from the beginning of the file instead.



Fixed an issue whereby, virtual repositories containing remote repositories with no metadata were not visible to non-admin users.



Fixed an issue that prevented an Artifactory system import from completing successfully when a Federated repository is active.



Fixed an issue whereby, Artifactory failed to initialize in an Artifactory Windows installation due to the incorrect loading of the JDBC driver. The JDBC drivers are now automatically copied to the $JFROG_HOME/artifactory/app/artifactory/tomcat/lib folder during installation on Windows.



Full Sync operations on Federated repositories now always update the timestamp in the node_event_cursor table.



Fixed an issue in the batch propagation mechanism for Full Sync operations that sometimes caused parsing exceptions. In addition, a new retry mechanism will fail only after a defined number of attempts. (By default, Full Sync will fail if a batch fails to propagate 5 times.)



Fixed an issue whereby Full Sync operations could not be triggered again after failing the initial attempt.



Fixed an issue whereby, custom CA certificates could not be added to Artifactory in an OpenShift installation.