Artifactory 7.59

JFrog Release Information
Content Type
Release Notes

Issue ID

Description

Fix Version

Additional Information

RTDEV-33212

When using an Access Token with a scope of applied-permissions/groups Artifactory may return a 400 Username cannot be null error on some endpoints in the repositories' resource.

7.59.12

 

RTDEV-34369

When updating Artifactory to version 7.59, under some circumstances, users who attempt to modify their binary-store.xml configuration file might experience files being deleted.

7.59.16

Users with Sharding Cluster configured with Eventual Cluster are at risk of experiencing this issue.

RTDEV-34236

When using Artifactory versions newer than 7.56, under certain circumstances some large accounts might experience a high query load to the database, causing it to crash.

Customers with the one of following account specifications should use the workaround specified:

  • A database Nodes table containing over 50 million rows

  • Over 5% of the database Nodes table contents refer to Docker images or Maven packages

7.68.x

Workaround: To avoid this issue, set the following system property: artifactory.file.service.cache.enabled=false

Note

If your virtual repositories point to less than 10 local repositories each, it is recommended to disable this feature using the system property above.

It is also possible to manually create the index before upgrading to reduce the risk of performance degradation.

For more information, see Internal Database Indexing Enhancements for Nodes Table.

RTDEV-38832

Customers in versions 7.59.x-7.63.5 who created authentication SSH keys under User Profile and then upgraded to a newer version will lose the saved authentication SSH keys.

7.71.16

Check if your SSH keys have been lost, and if so, upgrade Artifactory to version 7.71.16 and recreate the SSH keys.

If you used the Join Key to register a remote JPD, the Mission Control microservice in the home JPD fails to connect to the remote JPD and the remote JPD appears as offline in the topology after a certain period.View the Join Key

The remote JPD's Access microservice fails to recognize the home JPD's Mission Control microservice and marks it as a stale service. The Access cleanup process revokes the join key.

As a result, you cannot distribute release bundles to the remote JPD, access federation with the remote JPD fails, and license buckets are affected.

Solution: Re-register the remote JPDs that you registered using join keys with Pairing Tokens before you upgrade.Pairing Tokens