Artifactory 7.49

RTDEV-30171

New Content-Disposition Header can cause failures in some instances.

7.59.9

RTDEV-29791

NuGet authentication with Access Token stopped working when NugetResourceSelector was introduced.

7.53.4

RTDEV-29837

Artifactory stopped responding following threads blocked on getAllBuildInfoRepos.

7.49.6

RTDEV-28985

An issue related to the new Federated repository Multi-Version feature disables Federated repositories after upgrading a JPD from 7.49.3 or 7.49.5 to any later version.

7.49.6

Workaround:

Customers with Federated repositories who previously had Artifactory 7.49.3 or 7.49.5 installed must run the API described below after upgrading any JPDs to a later version.

Disabled repositories for each JPD can be re-enabled manually using the following API:

curl -X POST -uadmin:password "https://<your_URL>/artifactory/api/federation/repos/enable" -H "Content-Type: application/json" -T enable.json

To enable repositories of specific types, add the following to  enable.json:

["Alpine", "generic", "conan", "docker", "maven", "npm", "yum"]

To enable all repositories:

["*"]

RTFACT-27474

When configuring repository replication, if the  enableEventReplication  and  syncDeletes  parameters were both enabled and then  syncDeletes  is disabled via REST API, both parameters are disabled.

7.49.6

Suggested Fix:

To overcome this issue, send a POST call with explicit values for both properties. For example:

{         

     "enableEventReplication": true,         
       "syncDeletes":true      
 }

JFUI-11925

Artifactory unable to restart due to Frontend python3 dependency on Centos7/RHEL7.

7.49.10

RTFACT-29316

Artifactory could not install modules and providers from https://registry.terraform.io/ since Terraform Registry changed the CDN Providers on Jan 18th, 2023. This update changes the responses to the HEAD requests sent by the Artifactory remote repository to the Terraform Registry from 200 (Success) to 405 (Method not allowed) error.

7.55.x

Suggested Fix:

Enable "Bypass HEAD Requests" in the Terraform Remote repository configurations.Advanced Settings for Remote Repositories

JFUI-11951

Selecting the "Attach License" screen does not display the JPD names.

7.49.6

An empty error message is displayed when trying to attach a license where in the expected license count is zero.

RTFACT-27545

OpenJdk17.0.3, which is bundled with Artifactory 7.46/7.47/7.49 has a bug in the newrelic java agent, which causes Artifactory to fail to start up.

7.49.6

RTFACT-29308

The creation of new indexes might fail during the Artifactory upgrade for customers with Microsoft SQL Server (MSSQL) running with non-enterprise edition, since ‘online index’ operations are not available in every SQL Server edition.

JA-4703

Any changes made to the security configurations UI will override the custom configurations defined in the Access YAML Configuration.Introduction to the General Security SettingsAccess YAML Configuration

7.49.5,

7.50.3

Customers with an Enterprise+ subscription that have Access Federation enabled will lose the Access Federation setup as a result of editing the security configurations WebUI.Introduction to the General Security Settings

RTFACT-29273

Due to MSSQL limit of number of parameters that a parameterized query can have (2100), an Artifactory with more than 300 repositories will not start after upgrading to version 7.49.5.

7.49.5

Workaround:

After the upgrade, place the parameter artifactory.repo.config.db.query.batch.size = 100 in artifactory.system.properties and start Artifactory.

RTDEV-29281

The maxUniqueSnapshots are not saved when the value is changed in remote repositories.

7.49.5

JFUI-11773

In some cases, users are unable to login to the JFrog Platform when using Google Multi-Factor Authentication.

7.49.5

Workaround:

Clear the browser cache and refresh the JFrog UI before attempting to login. If that does not work, disable Google Multi-Factor Authentication by removing the parameter - "google" from the access.config.latest.yml file.