Artifactory 7.71.2 Self-Hosted

JFrog Release Information

ft:sourceType
Paligo

Released: 24 October, 2023

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

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

Breaking Change for Authentication Provider Configuration

As part of Artifactory version 7.71.2 upgrade, Artifactory seamlessly migrates all custom authentication provider configuration for LDAP and Crowd from the Artifactory System Properties to Access YAML configuration. After the upgrade, you must make all changes to the relevant authentication provider properties in the Access YAML Configuration. For more information, see Migrated Authentication Provider Properties.Access YAML ConfigurationMigrated Authentication Provider Properties

Breaking Change: Legacy member-of-groups:"*" scope is no longer accepted in Accesss Tokens

In Artifactory 7.71.2, due to a parsing issue with the scope, member-of-groups:"*" , the scope for access tokens are not parsed correctly and does not provide user-scoped token permissions to the token.

To workaround the issue, you can create a token with the same scope without the quotes - member-of-groups:* . You can also use the scope, applied-permissions/user, which replaces the legacy, member-of-groups:* token scope.

Known Issue in This Version

Artifactory failed to pull Go Submodules of packages when the remote repository is pointed to github.com. For more information, see Known Issues.

Known Issue in This Version

When enabling the setting Bypass HEAD Requests for one or more remote repositories, a connection leak might occur. For more information, see Known Issues.

New Features

  • Self-Hosted Support for Hugging Face ML Repositories (Beta release)  

    JFrog now supports local and remote Hugging Face repositories in Self-Hosted instances, allowing you to use Artifactory to house ML models alongside your other software components and Xray to detect malicious models and enforce license compliance. For more information, see Hugging Face Repositories.Hugging Face Repositories

Feature Enhancements

  • Configuration Settings Added to Cached Filesystem Binary Provider 

    The following two configuration settings were added to cache-fs, the Cached Filesystem Binary Provider:

    • maxFileSizeLimit: Set the maximum limit for a binary to be saved in the cache-fs layer.

    • skipDuringUpload: A flag that allows you to skip saving binaries to cache-fs during upload requests.

    For more information, see Cached Filesystem Binary Provider.Cached Filesystem Binary Provider

  • Migration of Authentication Provider Configuration from Artifactory Service to Access Service  

    As part of enhancements to the JFrog Access Service to make it the primary service for authentication providers, from Artifactory version 7.71.x, the functionality for the following authentication providers has moved to the Access Service: Internal, LDAP, HTTP SSO, and Crowd/JIRA.Migrated Authentication Provider Properties

Resolved Issues

JIRA Issue

Description

RTFACT-29895 

Fixed an issue related to Terraform whereby, when trying to resolve modules from a smart repository, Artifactory returned a 404 error.

RTFACT-29886 

Fixed an issue related to Conda whereby, Artifactory did not support retrieving artifact metadata from remote repositories that use the .ZST compression algorithm.

RTFACT-29862 

Fixed an issue whereby Federated repositories did not stay in sync after files were cleaned up by a plugin.

RTDEV-36089

Fixed an issue related to Docker whereby, when trying to perform orphan layer cleanup on an Artifactory instance with S3, a connection leak might occur.

RTDEV-31458

Fixed an issue whereby, under certain circumstances, the performance of virtual PyPI repositories with multiple local repositories was impaired.

JA-5100

Fixed an issue whereby, when authenticating using LDAP in an environment containing several LDAP settings, Artifactory searched for the user's group association across all group settings, instead of only in the paired LDAP setting.