Artifactory 7.61

Issue ID	Description	Fix Version	Additional Information
RTFACT-29709	The Docker Tag Retention setting does not perform as expected for multi-architecture images. Images under `manifest.list` are currently excluded from the retention logic and therefore are not deleted once the Docker Tag Retention limit is exceeded.
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

Issue ID

Description

Fix Version

Additional Information

RTFACT-29709

The Docker Tag Retention setting does not perform as expected for multi-architecture images. Images under manifest.list are currently excluded from the retention logic and therefore are not deleted once the Docker Tag Retention limit is exceeded.

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