Artifactory 7.63.7 Self-Hosted

JFrog Release Information


Released: 24 July, 2023

API Key Deprecation

As notified in Artifactory 7.47.10, support for API Key is slated to be removed in a future release. To ease customer migration to reference tokens, which replaces API key, we are disabling the ability to create new API keys at the end of Q3 2024. The ability to use API keys will be removed at the end of Q4 2024. For more information, see JFrog API Key Deprecation Process.User ProfileJFrog API Key Deprecation Process

Known Issue in this Version

under some circumstances, users who attempt to modify their binary-store.xml configuration file might experience files being deleted. Users with Sharding Cluster and Eventual Cluster configured should upgrade to version 7.63.11 or higher. For more information, see Known Issues.

Join Key issue when you upgrade to Artifactory 7.59.9 - 7.63.7

If you used 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.Join Key


This issue occurs because the Access microservice in the remote JPD fails to recognize the Mission Control microservice of the home JPD and marks it as a stale service. When the Access cleanup process runs, the join key is revoked.


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


To avoid this issue, you must re-register the remote JPDs that you registered using join keys with Pairing Tokens before you upgrade.Pairing Tokens

If you upgraded to an affected version, you must re-register the remote JPDs with Pairing Tokens so the remote JPDs are accessible again.Pairing Tokens

Feature Enhancements

Monitoring Federated Repositories using Open Metrics

Self-hosted customers can now gather Federation performance data in a structured log file using a set of metrics that complies with the Open Metrics standard. This data can then be accessed by 3rd party monitoring tools without the need for custom inbound API calls.Open Metrics

For more information, see Monitor Federated Repositories using Open Metrics.Monitor Federated Repositories using Open Metrics

Resolved Issues

JIRA Issue



Fixed an issue related to Storage Monitoring in the WebUI whereby, the storage quota warning and limit did not work as expected.


Fixed an issue related to Conda whereby, under some circumstances, certain packages were not indexed as expected.


Fixed an issue that prevented Release Bundle v2 database tables from being created on Edge devices and Cold Storage instances.