Artifactory 7.71.5 Self-Hosted

JFrog Release Information


Released: 21 November, 2023

Feature Enhancements

  • Additional Package Types added for Cold Storage Archiving

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

Resolved Issues

JIRA Issue



Fixed an issue related to the Get All Repositories Configurations REST API whereby, the response did not include all the required fields for generic remote repositories.


Fixed an issue related to npm whereby, when trying to resolve an artifact from a smart remote repository pointing to an npm repository, Artifactory returned an incorrect response code.


Fixed an issue related to the List Docker Tags REST API whereby, Artifactory did not return the full tags list in cases of a large number of pages.


Fixed an issue whereby, when trying to browse repositories using SAML login in an instance with Anonymous Access enabled, Artifactory returned an error and did not automatically redirect to the login page for authentication.


Fixed an issue related to Terraform whereby, Terraform Backend repositories did not support using client versions 1.6 and above.


Fixed an issue whereby when the binary store is configured with sharding or a sharding cluster and a remote connection reset occurs, Artifactory would sometimes incorrectly cache a portion of a binary and subsequently serve it to users.


Fixed an issue related to the docker tags/list REST API whereby, when using the endpoint in a remote repository pointing to a Ret Hat registry with Include Patterns enabled, Artifactory did not return the tags list.


Fixed an issue whereby, when blocking replication on the remote Artifactory instance, the event-based pull replication on the configured instance will crash and will not resume even after allowing replication on the remote Artifactory instance again.


Fixed an issue whereby, a token that has username scope in the form of `*@*` were not identified as identity tokens.


Fixed an issue whereby, an LDAP DN such as username or group name with special characters ( for example, ("/"), was displayed as an invalid entity.


Fixed an issue whereby, a user's token still worked after the user was disabled in the LDAP configuration but existed in the JFrog Platform. Now, after a user is deactivated on LDAP side, we revoke the token immediately in the JFrog Platform.


Fixed an issue whereby, the buffer timeout was higher than the actual timeout in Access Federation, which resulted in only one batch of changes would be published and the changes thereafter in the buffer would get lost because of the timeout.